-
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
RDB Loader: fix eventual consistency problem #3113
Comments
chuwy
changed the title
Relational Database Loader: fix eventual consistency problem
RDB Loader: fix eventual consistency problem
Feb 20, 2017
Good talk on this issue and some potential solutions... https://spark-summit.org/east-2017/events/spark-and-object-stores-what-you-need-to-know/ |
chuwy
added a commit
that referenced
this issue
Jun 27, 2017
chuwy
added a commit
that referenced
this issue
Jun 28, 2017
chuwy
added a commit
that referenced
this issue
Jun 29, 2017
chuwy
added a commit
that referenced
this issue
Jun 30, 2017
chuwy
added a commit
that referenced
this issue
Jul 3, 2017
chuwy
added a commit
that referenced
this issue
Jul 8, 2017
chuwy
added a commit
that referenced
this issue
Jul 26, 2017
BenFradet
pushed a commit
that referenced
this issue
Aug 2, 2017
This was referenced Aug 21, 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
We have a problem with users who a) have large volumes and b) have high event/context cardinalities where:
COPY
statement (correctly) does not find this ghost folder (nor any contents of it), and thusCOPY
statement (correctly) failsWe need to fix this - we can hope that just porting the StorageLoader S3 folder discovery code might make the problem go away, but it would be better to actively guard against this issue in this release.
/cc @leonmaas
The text was updated successfully, but these errors were encountered: