[
https://issues.apache.org/jira/browse/SOLR-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968331#comment-15968331
]
Dennis Gove commented on SOLR-10486:
------------------------------------
The switch clauses in {code}evaluate(....){code} result in the same code path
for every tuple in the stream. It would be more efficient to construct a lambda
with the appropriate code during construction of this class (or on open) and
execute that in evaluate.
> Add Length Conversion Evaluators
> --------------------------------
>
> Key: SOLR-10486
> URL: https://issues.apache.org/jira/browse/SOLR-10486
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Joel Bernstein
> Attachments: SOLR-10486.patch
>
>
> Based on the work in SOLR-10485 I think it makes sense to add Conversion
> evaluators. I think a good place to start is with the conversions listed here:
> https://www.learner.org/interactives/metric/conversion_chart.html#1
> This ticket will add length conversions and lay down the initial syntax.
> Sample syntax:
> {code}
> select(eval(), convert(inches, meters, 22) as meters)
> {code}
> This will return a single tuple with 22 inches converted to meters.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
