You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cassandra Targett (JIRA)" <ji...@apache.org> on 2018/02/01 23:03:00 UTC
[jira] [Resolved] (SOLR-11283) Refactor all Stream Evaluators in
solrj.io.eval to simplify them
[ https://issues.apache.org/jira/browse/SOLR-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cassandra Targett resolved SOLR-11283.
--------------------------------------
Resolution: Fixed
Fix Version/s: 7.1
master (8.0)
I think this just got missed to be resolved - it's listed in CHANGES for 7.1 and was mentioned in the release notes. Please reopen if there's more to do.
> Refactor all Stream Evaluators in solrj.io.eval to simplify them
> ----------------------------------------------------------------
>
> Key: SOLR-11283
> URL: https://issues.apache.org/jira/browse/SOLR-11283
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Dennis Gove
> Assignee: Dennis Gove
> Priority: Major
> Fix For: master (8.0), 7.1
>
> Attachments: SOLR-11283.patch, SOLR-11283.patch
>
>
> As Stream Evaluators have been evolving we are seeing a need to better handle differing types of data within evaluators. For example, allowing some to evaluate over individual values or arrays of values, like
> {code}
> sin(a)
> sin(a,b,c,d)
> sin([a,b,c,d])
> {code}
> The current structure of Evaluators makes this difficult and repetitive work.
> Also, the hierarchy of classes behind evaluators can be confusing for developers creating new evaluators. For example, when to use a ComplexEvaluator vs a BooleanEvaluator.
> A full refactoring of these classes will greatly enhance the usability and future evolution of evaluators.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org