capistrant commented on code in PR #19051:
URL: https://github.com/apache/druid/pull/19051#discussion_r2853932220
##########
indexing-service/src/main/java/org/apache/druid/indexing/compact/CascadingReindexingTemplate.java:
##########
@@ -217,6 +243,118 @@ private static boolean intervalEndsAfter(Interval
interval, DateTime boundary)
return interval.getEnd().isAfter(boundary);
}
+ /**
+ * Generates a timeline view showing the search intervals and their
associated reindexing
+ * configurations. This is useful for operators to understand how rules are
applied across
+ * different time periods and to preview the effects of rule changes before
they are applied.
+ *
+ * @param referenceTime the reference time to use for computing rule periods
(typically DateTime.now())
+ * @return a view of the reindexing timeline with intervals and their configs
+ */
+ public ReindexingTimelineView getReindexingTimelineView(DateTime
referenceTime)
Review Comment:
hmm. I wonder about how we'd manage to re-use a lot of the underlying
private implementation details that are quite convoluted (unfortunately). Like
creating the base timeline from segment gran rules and what not is all shared
between the timeline creation and the task creation. I agree that it feels a
little weird here, but I didn't know how else to approach it without either
duping a lot of internal logic or exposing it to both somehow. will keep
thinking though
--
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]
