[ 
https://issues.apache.org/jira/browse/SOLR-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Potter updated SOLR-5654:
---------------------------------

    Attachment: SOLR-5654.patch

Here's an updated patch that uses a custom SynonymMap.Parser implementation 
instead of the SolrResourceLoader adapter approach based on the excellent 
suggestion by Steve Rowe. The only caveat is this requires making the 
SynonymFilterFactory.loadSynonyms method protected instead of private, which 
seemed like a good trade-off for being able to plug-in a different parser 
implementation.

I've also improved the test logic to verify synonyms get applied correctly 
after core reload. Lastly, I cleaned up a bit of the ignoreCase handling code, 
such as lowercasing keys / values when building the internal data structures 
when ignoreCase == true.

> 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
>         Attachments: SOLR-5654.patch, SOLR-5654.patch, SOLR-5654.patch, 
> SOLR-5654.patch
>
>
> 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.2#6252)

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

Reply via email to