[
https://issues.apache.org/jira/browse/SOLR-15701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430495#comment-17430495
]
David Eric Pugh commented on SOLR-15701:
----------------------------------------
Nice find! Assuming there is a 8.11, could we make this change for 9? It
feels weird to have a rename like this happen in a 9.1 versus a 9.0.. The
upgrade to 9 should be a real effort to validate your setup, clean up any cruft
that has built up for any Search Team. So having this change show up there
would be okay...
> ConfigSet SolrJ API is incomplete
> ---------------------------------
>
> Key: SOLR-15701
> URL: https://issues.apache.org/jira/browse/SOLR-15701
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: configset-api
> Affects Versions: 8.10
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
