Skip to content

SOLR-17398: Link V1 collection operations to their V2 equivalents - #5053

Open
serhiy-bzhezytskyy wants to merge 1 commit into
apache:mainfrom
serhiy-bzhezytskyy:SOLR-17398-javadoc-v2-links
Open

serhiy-bzhezytskyy wants to merge 1 commit into
apache:mainfrom
serhiy-bzhezytskyy:SOLR-17398-javadoc-v2-links

Conversation

@serhiy-bzhezytskyy

Copy link
Copy Markdown
Contributor

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

Description

The V1 collection operations that do not simply call a V2 class give no hint where the V2 equivalent is.

Solution

CollectionsHandler gets a Javadoc link to the V2 class, with its path and command, on the ten operations that have none. Two, REINDEXCOLLECTION and DISTRIBUTEDAPIPROCESSING, say there is no V2 equivalent yet. Javadoc only. Written with Claude Code.

Tests

./gradlew check -x test is clean (rat skipped); the links are resolved by the Javadoc build.

Checklist

  • I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
  • I have created a Jira issue and added the issue ID to my pull request title.
  • I have given Solr maintainers access to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation)
  • I have developed this patch against the main branch.
  • I have run ./gradlew check.
  • I have added tests for my changes.
  • I have added documentation for the Reference Guide
  • I have added a changelog entry for my change

Ten CollectionsHandler operations do not simply call a V2 class, so nothing told a reader where the V2 equivalent is. Each now says so in its Javadoc, or says that there is none yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant