[
https://issues.apache.org/jira/browse/SOLR-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119915#comment-15119915
]
Jason Gerlowski commented on SOLR-7981:
---------------------------------------
Hi Shashank,
Technically, the issue is still "open". The change requested by this JIRA *is*
still totally possible. But after [[email protected]]'s comment above,
it's not really clear whether it's desired. As Chris mentioned above, he
requested this feature, but that was based on a misconception of the current
behavior.
It might still make sense to make this change. But it's unclear whether
there's any desire for this feature, and/or whether it'd be worth
initial/ongoing effort.
So when I saw Chris' ambivalent comment above, I took that as a sign that this
wasn't wanted/needed, and I stopped working on this. I'm happy to resume work
on this if it turns out that others would find that work useful.
Were you asking because you'd like to see this feature get in, or were you just
asking for clarification/some-other-reason?
> 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
> Attachments: SOLR-7981.patch
>
>
> 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]
