You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Christian Moen (Created) (JIRA)" <ji...@apache.org> on 2012/02/05 08:47:56 UTC
[jira] [Created] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Introduce default Japanese stoptags and stopwords to Solr's example configuration
---------------------------------------------------------------------------------
Key: SOLR-3097
URL: https://issues.apache.org/jira/browse/SOLR-3097
Project: Solr
Issue Type: Improvement
Components: Schema and Analysis
Affects Versions: 3.6, 4.0
Reporter: Christian Moen
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Christian Moen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201039#comment-13201039 ]
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: https://issues.apache.org/jira/browse/SOLR-3097
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201220#comment-13201220 ]
Robert Muir commented on SOLR-3097:
-----------------------------------
I think it should be a convenience? Because the files do rarely change...
And I fear any automated method would end out just overwriting peoples work
if they try to tweak these files.
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202448#comment-13202448 ]
Robert Muir commented on SOLR-3097:
-----------------------------------
I think we are ready to move forward here actually.
The only modification I want to do is to put this stuff in the conf/lang/ directory,
instead of conf/ directly.
I created SOLR-3105 which uses the same scheme across other languages and it seems
much more organized this way.
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Christian Moen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202438#comment-13202438 ]
Christian Moen commented on SOLR-3097:
--------------------------------------
Robert, I agree.
Would a patch that contains your {{build.xml}} changes and the synched {{stopwords_ja.txt}} and {{stoptags_ja.txt}} files be a suitable next step? Please advise. Many thanks.
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Christian Moen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Moen updated SOLR-3097:
---------------------------------
Attachment: SOLR-3097.patch
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 3.6, 4.0
> Reporter: Christian Moen
> Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Christian Moen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200686#comment-13200686 ]
Christian Moen commented on SOLR-3097:
--------------------------------------
Patch for {{trunk}} and {{branch_3x}} attached.
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 3.6, 4.0
> Reporter: Christian Moen
> Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Christian Moen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200752#comment-13200752 ]
Christian Moen commented on SOLR-3097:
--------------------------------------
Thanks a lot, Robert.
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 3.6, 4.0
> Reporter: Christian Moen
> Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Robert Muir (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved SOLR-3097.
-------------------------------
Resolution: Fixed
Fix Version/s: 4.0
3.6
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 3.6, 4.0
> Reporter: Christian Moen
> Fix For: 3.6, 4.0
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200749#comment-13200749 ]
Robert Muir commented on SOLR-3097:
-----------------------------------
{quote}
(Longer term, I think should reconsider our overall approach to this across all languages, but that's perhaps a separate discussion.)
{quote}
It is a larger issue... in general we should make it easier to keep the two synchronized, but off the top of my head an idea for a plan was:
* add 'snowball format' support to solr stopfilter so it can read all the lucene stopwords directly
* add an ant task to synchronize the solr example from lucene's resources.
* (of course) add fieldtypes that actually use all these files.
On the other hand, realistically these resources are pretty static (don't change once added). So for now I don't think its a huge
risk that we don't have an auto-sync process... but we need to tackle these problems to easily integrate european languages anyway.
So I dont think this should block this issue, lets get japanese up and going for now.
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 3.6, 4.0
> Reporter: Christian Moen
> Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3097) Introduce default Japanese stoptags
and stopwords to Solr's example configuration
Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated SOLR-3097:
------------------------------
Attachment: SOLR-3097.patch
ok this ant task was easy enough to write...
here's my first stab at it.
> Introduce default Japanese stoptags and stopwords to Solr's example configuration
> ---------------------------------------------------------------------------------
>
> Key: SOLR-3097
> URL: https://issues.apache.org/jira/browse/SOLR-3097
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org