HADOOP-16118. S3Guard to support on-demand DDB tables (branch-3.2). #731
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
I got a failure in a test run. Unrelated to this patch (the fix is one of the predecessor patches to This will bring 3.2 close to 3.3 |
This is the first step for on-demand operations: things recognize when they are using on-demand tables, as do the tests. Branch-3.2 patch; test run failing for unrelated changes to the AbstractS3GuardToolTestBase test suite, which highlight that we have enough S3Guard changes in trunk it's time to backport one by one. Contributed by Steve Loughran. Change-Id: I44cf87a2bd253b78c2d0414e4be20e920027c980
steveloughran
force-pushed
the
s3/HADOOP-16118-DDB-on-demand-branch-3.2
branch
from
f950e4f to
3452d83
Compare
Contributor
Author
|
accidentally committed using the yetus email addr (still need to get an official ASF alias for that, so resubmitted) |
steveloughran
changed the title
Contributor
Author
|
No Yetus run; will push as a .patch |
| bills when it is not. | ||
|
|
||
| Before DynamoDB On-Demand was introduced, autoscaling was the sole form | ||
| of dynamic scaling. |
|
💔 -1 overall
This message was automatically generated. |
shanthoosh
pushed a commit
to shanthoosh/hadoop
that referenced
this pull request
Oct 15, 2019
This PR converts a hard-check that fails in case of regex-defined input if there is an overlap between regex-input and task-input, to a warning. Why? Because with Samza 1.0, rewrite is called multiple times to expand system descriptors, input descriptors, etc. This hard-check fails in this case causing deployment to stall. Therefore we convert it to a warning. NOTE: This now allows users to define stream config for their inputs which may overlap with regex-input. This was earlier explicitly disallowed by the hard-check. Author: rmatharu@linkedin.com <rmatharu@linkedin.com> Reviewers: Prateek Maheshwari <pmaheshwari@apache.org> Closes apache#731 from rmatharu/regexcheck
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
Contributor
Author
|
abandoning; moot now you don't need s3guard no more |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first step for on-demand operations: things recognize when they are using on-demand tables,
as do the tests.
Branch-3.2 patch; test run failing for unrelated changes to the AbstractS3GuardToolTestBase test suite,
which highlight that we have enough S3Guard changes in trunk it's time to backport one by one.
Contributed by Steve Loughran.
Change-Id: I44cf87a2bd253b78c2d0414e4be20e920027c980