capistrant opened a new pull request, #19106: URL: https://github.com/apache/druid/pull/19106
<!-- Thanks for trying to help us make Apache Druid be the best it can be! Please fill out as much of the following information as is possible (where relevant, and remove it when irrelevant) to help make the intention and scope of this PR clear in order to ease review. --> <!-- Please read the doc for contribution (https://github.com/apache/druid/blob/master/CONTRIBUTING.md) before making this PR. Also, once you open a PR, please _avoid using force pushes and rebasing_ since these make it difficult for reviewers to see what you've changed in response to their reviews. See [the 'If your pull request shows conflicts with master' section](https://github.com/apache/druid/blob/master/CONTRIBUTING.md#if-your-pull-request-shows-conflicts-with-master) for more details. --> <!-- Replace XXXX with the id of the issue fixed in this PR. Remove this section if there is no corresponding issue. Don't reference the issue in the title of this pull-request. --> <!-- If you are a committer, follow the PR action item checklist for committers: https://github.com/apache/druid/blob/master/dev/committer-instructions.md#pr-and-issue-action-item-checklist-for-committers. --> ### Description <!-- Describe the goal of this PR, what problem are you fixing. If there is a corresponding issue (referenced above), it's not necessary to repeat the description here, however, you may choose to keep one summary sentence. --> <!-- Describe your patch: what did you change in code? How did you fix the problem? --> <!-- If there are several relatively logically separate changes in this PR, create a mini-section for each of them. For example: --> After taking the initial implementation of the CascadingReindexingTemplate and associated RuleProvider concepts for a spin, some refactoring opportunities have been identified. I hope that these will make more conceptual sense to operators trying to configure this as well as make things generally easier to reason about. #### Rule Type Refactoring `ReindexingSegmentGranularityRule` and `ReindexingTuningConfigRule` have been deleted. ##### ReindexingPartitioningRule This new rule type consolidates partitioning details into a single rule. This rule takes the place of `ReindexingSegmentGranularityRule` in that it has special consideration for creating the base timeline of reindexing search intervals and that all search intervals created align to natural Segment Granularity boundaries being applied. The components of this rule are: * [required] Segment Granularity (Limited to the same strict set of granularities that the original rule type was) * [required] Partition Spec * [optional] virtual columns * This is an integration with #19061 so that the new range partitioning with expressions is supported by reindexing ##### ReindexingIndexSpecRule A new rule type that is scoped to the `IndexSpec` that goes in a task tuning config. #### `CascadingReindexingTemplate` new top level fields I have considered combining the below 2 + defaultSegmentGranularity into a defaultPartitioningSomething top level field but did not do this as of now. ##### `defaultPartitionsSpec` Required partitionsspec that will be applied in cases where a synthetic `ReindexingPartitioningRule` needs to be generated to complete the reindexing timeline ##### `defaultPartitioningVirtualColumns` Optional default partitioning virtual column expressions that would be used if your default partitionspec utilized the new functionality in #19061 ##### `tuningConfig` `CascadingReindexingTemplate` now has an optional top level `tuningConfig` field where an operator can provide a `UserCompactionTaskQueryTuningConfig` that will apply to all tasks generated by the supervisor. Note that any partitions spec here is useless and will be blown away by either the defaultPartitionsSpec or the applicable ReindexingPartitioningRule's partition spec. IndexSpec however can take a default here that will apply in any case where there is not an IndexSpecRule that applies to the task being generated <!-- In each section, please describe design decisions made, including: - Choice of algorithms - Behavioral aspects. What configuration values are acceptable? How are corner cases and error conditions handled, such as when there are insufficient resources? - Class organization and design (how the logic is split between classes, inheritance, composition, design patterns) - Method organization and design (how the logic is split between methods, parameters and return types) - Naming (class, method, API, configuration, HTTP endpoint, names of emitted metrics) --> <!-- It's good to describe an alternative design (or mention an alternative name) for every design (or naming) decision point and compare the alternatives with the designs that you've implemented (or the names you've chosen) to highlight the advantages of the chosen designs and names. --> <!-- If there was a discussion of the design of the feature implemented in this PR elsewhere (e. g. a "Proposal" issue, any other issue, or a thread in the development mailing list), link to that discussion from this PR description and explain what have changed in your final design compared to your original proposal or the consensus version in the end of the discussion. If something hasn't changed since the original discussion, you can omit a detailed discussion of those aspects of the design here, perhaps apart from brief mentioning for the sake of readability of this PR description. --> <!-- Some of the aspects mentioned above may be omitted for simple and small changes. --> #### Release note N/A for now but we will have a larger release note I can share encompassing all of the new reindexing rule provider stuff for druid 37. --> <hr> ##### Key changed/added classes in this PR * `CascadingReindexingTemplate` * `ReindexingConfigBuilder` * `ReindexingDeletionRuleOptimizer` * `ReindexingPartitioningRule` * `ReindexingIndexSpecRule` <hr> <!-- Check the items by putting "x" in the brackets for the done things. Not all of these items apply to every PR. Remove the items which are not done or not relevant to the PR. None of the items from the checklist below are strictly necessary, but it would be very helpful if you at least self-review the PR. --> This PR has: - [ ] been self-reviewed. - [ ] added documentation for new or modified features or behaviors. - [ ] a release note entry in the PR description. - [ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links. - [ ] added or updated version, license, or notice information in [licenses.yaml](https://github.com/apache/druid/blob/master/dev/license.md) - [ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader. - [x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for [code coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md) is met. - [ ] added integration tests. - [x] been tested in a test Druid cluster. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
