Adding LinearShardSpec and ACL on S3 object #77
Merged
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.
I added LinearShardingSpec under shard package and LinearPartitionChunk under partition package. This is a little different from SingleDimensionShardSpec. LinearShardSpec is necessary for increasing and decreasing druid realtime cluster size dynamically on demand. Meanwhile, SingleDimensionShardSpec requires predefined the number of shards.
I want to add REST_CANNED_BUCKET_OWNER_FULL_CONTROL to the s3 object. I know this might be very specific request in Netflix environment. The problem is, in eu-west-1 AWS, the account of druid ec2 instance is different from the account managing s3 bucket. So, without this ACL, lifecycle rule of s3 bucket is not being applied in eu-west-1. Also, you may know I cannot override the ACL out of druid core context.