Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOLR-15187: v2-POJO based SolrRequest classes #2422

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

gerlowskija
Copy link
Contributor

Description

The POJOs used for serialization/deserialization by some V2 APIs have a lot of duplication with the existing SolrRequest objects for those APIs.

Solution

Since they share the same fields, SolrRequest objects can be implemented using their v2-POJO counterparts.

Tests

None, yet.

Checklist

Please review the following and check all that apply:

  • 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)
  • I have developed this patch against the master branch.
  • I have run ./gradlew check.
  • I have added tests for my changes.
  • I have added documentation for the Ref Guide as appropriate (for Solr changes only).

This commit starts to have the Payload POJOs replace the fields in
individual CollectionAdminRequest classes.  Backup is pretty much
finished.  I started on REstore and ran into a hiccup with the
collection-creation params - I could handle these via map operations,
but that's not very clean or strongly typed.  So my next step needs to
be creating a class that CreatePayload and REstorePayload can share with
various collection-creation params.
This eliminates some duplication between the API-specific classes,
provides an extra prod to make sure devs keep V2 APIs up to date, and
gives us a path forward for v1-v2 randomization on POJO-based
v2 APIs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant