[jira] [Commented] (SOLR-7981) term based ValueSourceParsers should support an option to run an analyzer for hte specified field on the input

["Jason Gerlowski (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975387#comment-14975387 ] 

Jason Gerlowski commented on SOLR-7981:
---------------------------------------

Hi,

I'm trying to learn my way around Lucene, so I was planning on working on a patch for this JIRA.

Should I bring up on the mailing list that I'm working on this?  I know this is done for a lot of things, but I wasn't sure whether it was standard to do this for simple/uncontroversial patches as well.  I don't want to spam the list for unimportant things, though maybe that's the wrong attitude.

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org