[ 
https://issues.apache.org/jira/browse/SOLR-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879209#comment-13879209
 ] 

Michael McCandless commented on SOLR-5654:
------------------------------------------

bq. I guess your point is that we shouldn't be making this easier. 

Right.

bq. I disagree: the point of the issue is to allow people more fine-grained 
control over an already-existing freedom.

Just because there's already an existing (not necessarily good) freedom doesn't 
mean it must be made easier.  Optimize is an existing freedom :)

Does Solr at least record somewhere that "full re-index required"?  So the user 
(if s/he knows to look in the right place on the admin UI) is informed that 
inconsistent results might be because they didn't fully re-index yet...

> Create a synonym filter factory that is (re)configurable, and capable of 
> reporting its configuration, via REST API
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5654
>                 URL: https://issues.apache.org/jira/browse/SOLR-5654
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Schema and Analysis
>            Reporter: Steve Rowe
>
> A synonym filter factory could be (re)configurable via REST API by 
> registering with the RESTManager described in SOLR-5653, and then responding 
> to REST API calls to modify its init params and its synonyms resource file.
> Read-only (GET) REST API calls should also be provided, both for init params 
> and the synonyms resource file.
> It should be possible to add/remove/modify one or more entries in the 
> synonyms resource file.
> We should probably use JSON for the REST request body, as is done in the 
> Schema REST API methods.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to