[
https://issues.apache.org/jira/browse/SOLR-12139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417887#comment-16417887
]
David Smiley commented on SOLR-12139:
-------------------------------------
Cancel that +1. My concern with this patch is that it assumes that
StrDocValues is the only case in which strVal is the appropriate method to
call. There are intermediate FunctionValues like IfFunction that sit
in-between and would foil your attempt here. Perhaps we can think of
objectVal(...) as the always-correct way, and consider instanceof checks for
IntDocValues, FloatDocValues, etc. as optimizations? Such extensive instanceof
checks would ideally occur once and not for each doc.
> Support "eq" function for string fields
> ---------------------------------------
>
> Key: SOLR-12139
> URL: https://issues.apache.org/jira/browse/SOLR-12139
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search
> Reporter: Andrey Kudryavtsev
> Assignee: Mikhail Khludnev
> Priority: Minor
> Attachments: SOLR-12139.patch, SOLR-12139.patch, SOLR-12139.patch
>
>
> I just discovered that {{eq}} user function will work for numeric fields only.
> For string types it results in {{java.lang.UnsupportedOperationException}}
> What do you think if we will extend it to support at least some of string
> types as well?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
