[ https://issues.apache.org/jira/browse/SOLR-14907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215360#comment-17215360 ]
David Smiley commented on SOLR-14907: ------------------------------------- +1 to everything Noble said. V2 has been "the future" for many years and we need to get this on with. I think a challenge to all us maintainers is that there are plenty of old-school V1 style handlers to look at, and so it's natural to instinctively copy such an approach when making new handlers. I think we might do well to add a one-line comment at the start of every V1 handler definition to say "TODO convert to V2 API e.g. <classNameHere>" pointing to a spot you recommend we look at, preferably a location with good internal javadocs > 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