[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user sjwiesman commented on the issue: https://github.com/apache/flink/pull/4607 * clicked the wrong button ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user sjwiesman commented on the issue: https://github.com/apache/flink/pull/4607 I'm going to go ahead and close this pr and issue to avoid confusion. ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user aljoscha commented on the issue: https://github.com/apache/flink/pull/4607 @stevenzwu I'm afraid the currently isn't. But one should be started once work starts on the new sink for Flink 1.6 ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user stevenzwu commented on the issue: https://github.com/apache/flink/pull/4607 @aljoscha is there any doc/write-up about the reworking of BucketingSink? ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user aljoscha commented on the issue: https://github.com/apache/flink/pull/4607 I think we won't merge this as is. There are some thoughts flying around for reworking the BucketingSink to use our own `FileSystem` implementation and also making it work well with S3. I'm quite sure that this work will land in 1.6 but we have to release 1.5 now because it's already late. ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user narayaruna commented on the issue: https://github.com/apache/flink/pull/4607 @aljoscha can we merge this PR. This is very helpful to ingest data to S3 in a more reliable way. BucketingSink writing to S3 errors out making the data ingestion less reliable. ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user zentol commented on the issue: https://github.com/apache/flink/pull/4607 We cannot restart Travis ourselves. Only the contributor can schedule another run by adding another commit (even an empty one). However, please don't do that for the sake of getting a picture-perfect build; we are aware of some unstable tests and account for that in the review. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user sjwiesman commented on the issue: https://github.com/apache/flink/pull/4607 Would you be able to rerun travis, the test failed on a single configuration during the Kafka09ITTest due to a task manager failure. I do not believe any of my code changes touched any of the code paths in that test. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink issue #4607: [FLINK-6306][connectors] Sink for eventually consistent f...
Github user sjwiesman commented on the issue: https://github.com/apache/flink/pull/4607 CC: @aljoscha I screwed up the rebase so I cherry picked the updates into a new branch and re-opened the pr. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---