-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StorageLoader: replace table configuration property with schema #2458
Comments
chuwy
added a commit
that referenced
this issue
Jan 18, 2017
chuwy
added a commit
that referenced
this issue
Feb 20, 2017
chuwy
added a commit
that referenced
this issue
Feb 22, 2017
chuwy
added a commit
that referenced
this issue
Feb 27, 2017
chuwy
added a commit
that referenced
this issue
Feb 28, 2017
chuwy
added a commit
that referenced
this issue
Mar 13, 2017
chuwy
added a commit
that referenced
this issue
Mar 14, 2017
chuwy
added a commit
that referenced
this issue
Mar 14, 2017
chuwy
added a commit
to snowplow/snowplow-rdb-loader
that referenced
this issue
Sep 5, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem with the current approach is that it suggests that:
is safe. In fact, the above is highly unsafe - because both loads would populate the same child tables in
atomic
.For this reason, we should remove the end user control over the
events
table (which is currently the only table the user can rename) and replace the outdatedtable
option with aschema
option (correctly implying that each distinct Snowplow load needs to be sandboxed into its own schema).The text was updated successfully, but these errors were encountered: