[
https://issues.apache.org/jira/browse/SOLR-14907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214775#comment-17214775
]
Houston Putman commented on SOLR-14907:
---------------------------------------
+1 on supporting the V2 API, but since it fits fairly well into the V1 API I'm
not sure we should make it V2 only. And I like the suggested path, though I
might change file-name to be a urlParam instead of a part of the path, because
it could contain multiple {{/}}s, which might be confusing.
According to the ref guide, the UPLOAD configSet command does not have a V2 API
yet. Maybe we create another ticket to add a v2 command for configSet upload,
and this can be a part of that ticket.
> Support single file upload/overwrite in configSet API
> -----------------------------------------------------
>
> Key: SOLR-14907
> URL: https://issues.apache.org/jira/browse/SOLR-14907
> Project: Solr
> Issue Type: Improvement
> Components: configset-api
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Fix For: 8.7
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> After SOLR-10391 was implemented, users are now able to overwrite existing
> configSets using the configSet API. However the files uploaded are still
> required to be zipped and indexed from the base configSet path in ZK. Users
> might want to just update a single file, such as a synonyms list, and not
> have to tar it up first.
> The proposed solution is to add parameters to the UPLOAD configSet action, to
> allow this single-file use case. This would utilize the protections already
> provided by the API, such as maintaining the trustiness of configSets being
> modified.
> This feature is part of the solution to replace managed resources, which is
> planned to be deprecated and removed by 9.0 (SOLR-14766).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
