lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Moen (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags and stopwords to Solr's example configuration
Date Mon, 06 Feb 2012 05:17:59 GMT


Christian Moen commented on SOLR-3097:

Thanks, Robert.

Is your thinking to use the {{sync-analyzers}} target to automatically copy resources to the
right place as part of {{package}}, {{example}}, etc. -- or is this as convenience to easier
make sure the files are in sync when we check them in separately?

The {{sync-analyzers}} works fine for the latter purpose, but needs hookups elsewhere in {{build.xml}}
if we want to do this automatically.  Happy to follow up on the latter if this is what you'd
like to see in the patch.

> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>                 Key: SOLR-3097
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>    Affects Versions: 3.6, 4.0
>            Reporter: Christian Moen
>         Attachments: SOLR-3097.patch, SOLR-3097.patch
> SOLR-3056 discusses introducing a default field type {{text_ja}} for Japanese in {{schema.xml}}.
 This configuration will be improved by also introducing default stopwords and stoptags configuration
for the field type.  
> I believe this configuration should be easily available and tunable to Solr users and
I'm proposing that we introduce the same stopwords and stoptags provided in LUCENE-3745 to
Solr example configuration.  I'm proposing that files can live in {{solr/example/solr/conf}}
as {{stopwords_ja.txt}} and {{stoptags_ja.txt}} alongside {{stopwords_en.txt}} for English.
 (Longer term, I think should reconsider our overall approach to this across all languages,
but that's perhaps a separate discussion.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message