[
https://issues.apache.org/jira/browse/SOLR-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768800#action_12768800
]
Hoss Man commented on SOLR-1520:
--------------------------------
At first glance, this seems like it could be fixed by changing the two "new
TermQuery" lines to use FIeldType.readableToIndexed() ... but there's also some
funky stuff going on in ElevationComparatorSource that makes me think it's
probably not that easy ... particularly the use of getStringIndex which
suggests that the Trie Fields definitely won't work.
Anyone have any suggestions on a true fix for this, or at least a way to make
it fail cleanly with a good error message about the uniqueKey field type
expectations that it has?
> 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: search
> Affects Versions: 1.3
> Environment: Gentoo Linux, Apache Tomcat 6.0.20, Java 1.6.0_15-b03
> Reporter: Simon Lachinger
> 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.
-
You can reply to this email to add a comment to the issue online.
