Skip to content

SOLR-18359: remove CreateTimeRoutedAlias.setMaxFutureMs(Integer) overload - #4781

Open
serhiy-bzhezytskyy wants to merge 1 commit into
apache:mainfrom
serhiy-bzhezytskyy:SOLR-18359-remove-setmaxfuturems-integer
Open

SOLR-18359: remove CreateTimeRoutedAlias.setMaxFutureMs(Integer) overload#4781
serhiy-bzhezytskyy wants to merge 1 commit into
apache:mainfrom
serhiy-bzhezytskyy:SOLR-18359-remove-setmaxfuturems-integer

Conversation

@serhiy-bzhezytskyy

Copy link
Copy Markdown
Contributor

https://issues.apache.org/jira/browse/SOLR-18359

Removes the deprecated CollectionAdminRequest.CreateTimeRoutedAlias.setMaxFutureMs(Integer) overload, superseded by setMaxFutureMs(Long) since SOLR-15376. Zero real callers of the deprecated overload -- the one call site (TimeRoutedAliasUpdateProcessorTest) already passes a Long.

1 test, 0 failures (testMaxFutureMs, gated behind -Dtests.awaitsfix=true per its own @AwaitsFix(SOLR-13059)).

AI-assisted (Claude Sonnet 5)

…load

Deprecated since 9.0 in favor of setMaxFutureMs(Long). The one caller
(TimeRoutedAliasUpdateProcessorTest) already passes a Long, so it was
already resolving to the non-deprecated overload -- zero real callers
of the deprecated one.

@epugh epugh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice little clean up!

@epugh epugh self-assigned this Aug 21, 2026
@epugh

epugh commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Looking again, does this mean there is an opportuntiyt to remove a @AwaitsFix(SOLR-13059)) ???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants