[
https://issues.apache.org/jira/browse/SOLR-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170430#comment-13170430
]
Grant Ingersoll commented on SOLR-1520:
---------------------------------------
The only issue is TrieField returns true for isTokenized() which causes the
current approach to fail, but I guess we can just drop the isTokenized()
requirement since it's somewhat undefined anyway what an multi-token id field
means anyway. So, I'm just going to drop it and commit it w/ the only
requirement being that the unique key exists.
> QueryElevationComponent does not work when unique key is of type 'sint'
> -----------------------------------------------------------------------
>
> Key: SOLR-1520
> URL: https://issues.apache.org/jira/browse/SOLR-1520
> Project: Solr
> Issue Type: Bug
> Components: Rules, search
> Affects Versions: 1.3
> Environment: Gentoo Linux, Apache Tomcat 6.0.20, Java 1.6.0_15-b03
> Reporter: Simon Lachinger
> Assignee: Grant Ingersoll
> Fix For: 3.6, 4.0
>
> Attachments: SOLR-1520.patch, SOLR-1520.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> QueryElevationComponent does not work when unique key of the documents is of
> type 'sint'. I did not try any other combination, but when I looking at the
> source in QueryElevationComponent.java I doubt it will work with any other
> type than string.
> I propose to either make it work with other data types or at least to post a
> warning.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
