[
https://issues.apache.org/jira/browse/SOLR-15174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323843#comment-17323843
]
Jason Gerlowski commented on SOLR-15174:
----------------------------------------
I attached a patch to show how this can be fixed. It's missing a test, but is
otherwise ready to go.
I probably won't merge this patch though. I'm trying to help transition things
over to the new POJO model of v2-api-implementation when I find free time, and
I'm hoping to update MODIFYCOLLECTION in the next week or so. So I didn't want
to spend time running tests/precommit on this today, since i intend to rip out
the whole API-mapping implementation shortly.
Hopefully the patch can still serve serve as a good example for how to solve
these sort of v1<->v2 incompatibility issues though. And it can always be
taken forward if I have less free-time and it takes me longer to get to
MODIFYCOLLECTION than I hoped.
> v2 modify collection doesn't allow you to change the configset used.
> --------------------------------------------------------------------
>
> Key: SOLR-15174
> URL: https://issues.apache.org/jira/browse/SOLR-15174
> Project: Solr
> Issue Type: Bug
> Components: v2 API
> Affects Versions: main (9.0)
> Reporter: David Eric Pugh
> Priority: Minor
> Attachments: SOLR-15174.patch
>
>
> The v2 collection CREATE api lets you pick your configset via the `config`
> parameter, and in v1 with the `collection.configName`. So you would expect
> the modify command to work the same way, and indeed it works with v1, but not
> with v2. I have messed around with the apispec .json files, but didn't make
> much headway. {{}}{{}}
> Hoping someone smarter can pick this up!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
