[
https://issues.apache.org/jira/browse/SOLR-15701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075992#comment-18075992
]
Eric Pugh commented on SOLR-15701:
----------------------------------
I believe, after a long and winding journey, that we have completed this. I'd
love some review of the V2 configset upload apis (since that is our future!)
from those who have interacted on this ticket.
> ConfigSet SolrJ API is incomplete
> ---------------------------------
>
> Key: SOLR-15701
> URL: https://issues.apache.org/jira/browse/SOLR-15701
> Project: Solr
> Issue Type: Bug
> Components: configset-api, SolrJ
> Affects Versions: 8.10
> Reporter: Andrzej Bialecki
> Assignee: Eric Pugh
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.1
>
> Time Spent: 8h 40m
> Remaining Estimate: 0h
>
> SolrJ ConfigSet API allows users to manage configsets but it's curiously
> incomplete (and somewhat misleading):
> * CREATE action doesn't actually allow users to create a wholly new
> configset, it only allows to copy one of the existing configsets under a new
> name. It should really be renamed to COPY.
> * there's no support for UPLOAD action in the SolrJ API, which is a strange
> omission - there's support for every other action but there's no (easy) way
> to upload a new configset. {{ConfigSetHandler}} supports this action so the
> problem lies only in the missing client classes.
> I'll work on adding support for UPLOAD, but I'm not sure what to do with the
> mis-named CREATE - I'd love to rename it but this would cause back-compat
> issues. Maybe deprecate it, rename it only in 9.0 and keep supporting CREATE
> -> COPY until 9.1 release?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
