[
https://issues.apache.org/jira/browse/SOLR-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Gove updated SOLR-11283:
-------------------------------
Attachment: SOLR-11283.patch
All stream related tests pass.
The following 3 tests failed but appear to be completely unrelated to my
changes.
{code}
[junit4] Tests with failures [seed: EE1F61CDA04C3749]:
[junit4] - org.apache.solr.cloud.HttpPartitionTest.test
[junit4] - org.apache.solr.cloud.ForceLeaderTest.testReplicasInLIRNoLeader
[junit4] -
org.apache.solr.update.processor.UpdateRequestProcessorFactoryTest.testUpdateDistribChainSkipping
{code}
When run individually those tests pass.
> 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
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
