You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2013/04/13 23:26:15 UTC
[jira] [Commented] (SOLR-1401) solr should error on document
add/update if uniqueKey field has multiple tokens.
[ https://issues.apache.org/jira/browse/SOLR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631175#comment-13631175 ]
Erick Erickson commented on SOLR-1401:
--------------------------------------
SPRING_CLEANING_2013 JIRAS. I can freely define the ID field as text_en_splitting, index weird IDs, and get lots of documents. Seems like this is quite valid even today. Don't know how it plays with distributed indexing and doc routing though....
> solr should error on document add/update if uniqueKey field has multiple tokens.
> --------------------------------------------------------------------------------
>
> Key: SOLR-1401
> URL: https://issues.apache.org/jira/browse/SOLR-1401
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> over the years, have seem more then a few solr-user posts noticing odd behavior when using a uniqueKey field configured to use TextField with a non trivial analyzer ... we shouldn't error on TextField (KeyworkdTokenizer is perfectly legitimate) but we should error if that analyzer produces multiple tokens.
> Likewise we should verify that good error messages if uniqueKey field is configured such that multivalued=true.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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