[
https://issues.apache.org/jira/browse/SOLR-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976286#comment-14976286
]
David Smiley commented on SOLR-7981:
------------------------------------
What you should do is exactly what you just did -- announce your intention to
fix it on the issue. Most people don't even do that; it's only useful to
deconflict with someone else who may want to do it. All comments & JIRA issue
events get forwarded to Lucene's dev list; meaning your comment and mine right
now is CC'ed to the dev list.
> term based ValueSourceParsers should support an option to run an analyzer for
> hte specified field on the input
> --------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7981
> URL: https://issues.apache.org/jira/browse/SOLR-7981
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Labels: newdev
>
> The following functions all take exactly 2 arguments: a field name, and a
> term value...
> * idf
> * termfreq
> * tf
> * totaltermfreq
> ...we should consider adding an optional third argument to indicate if an
> analyzer for the specified field should be used on the input to find the real
> "Term" to consider.
> For example, the following might all result in equivilent numeric values for
> all docs assuming simple plural stemming and lowercasing...
> {noformat}
> termfreq(foo_t,'Bicycles',query) // use the query analyzer for field foo_t on
> input Bicycles
> termfreq(foo_t,'Bicycles',index) // use the index analyzer for field foo_t on
> input Bicycles
> termfreq(foo_t,'bicycle',none) // no analyzer used to construct Term
> termfreq(foo_t,'bicycle') // legacy 2 arg syntax, same as 'none'
> {noformat}
> (Special error checking needed if analyzer creates more then one term for the
> given input string)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
