[ https://issues.apache.org/jira/browse/SOLR-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984676#comment-14984676 ]
Hoss Man commented on SOLR-7981: -------------------------------- Wow ... I have no memory of creating this issue, even though it was only ~10 weeks ago ... which means i don't remember _why_ i created it, or _why_ i thought the default behavior was not to use an analyzer. Jason: your investigation appears to be correct - parseTerm does currently use getFieldQuery so the initial feature request is erroneous. Off the cuff i don't have a strong opinion about adding an option to specify an analyzer (or 'none') as a third arg to this method, but I guess i'd be hard pressed to argue against it since it was apparently my idea. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org