[
https://issues.apache.org/jira/browse/SOLR-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051811#comment-14051811
]
Houston Putman edited comment on SOLR-5963 at 7/3/14 7:45 PM:
--------------------------------------------------------------
[~hossman], sorry I just found this issue. I can address your concern about the
statistical expressions.
* I have no issue changing the name of Expressions to something that doesn't
conflict with existing lucene/solr stuff. I named it that because that is what
they are, mathematical expressions.
* The difference between the three can be confusing when you first look at it,
but I think the difference between "Aggregates" and the other two are pretty
self-explanatory when you start to actually use them. First of all "Aggregates"
aggregate unspecified amounts of data to a single value (such as median,
average, standard deviation, etc.) these are statistics tools. The other two
are a way of mapping(transforming/combining) one or more pieces of data into
one piece of data (this piece of data may be 0 or 1 dimensional, so a single
value or an array), these are regular mathematical tools like add, subtract,
multiply, etc. So you can use "Aggregate Mapping Operations/Expressions" and
"Field Mapping Operations" in the exact same way without thinking about it, the
only difference between the two is that one maps multiple lists into one list
and the other maps multiple values into one value.
Actually after typing this up I agree that the documentation of the feature
could be significantly improved, but I am not sure a syntactical difference
between aggregates and the other two are necessary since they don't share much
functionality (really just "sum" and "add"). Also the naming of "Aggregate
Mapping Operations/Expressions" and "Field Mapping Operations" should
definitely be changed.
* Ok, I'm confused about this point. "Field Mapping Operations" are ValueSource
parsers... I used existing ones and added some of my own.
was (Author: houstonputman):
[~hossman], sorry I just found this issue. I can address your concern about the
statistical expressions.
* I have no issue changing the name of Expressions to something that doesn't
conflict with existing lucene/solr stuff. I named it that because that is what
they are, mathematical expressions.
* The difference between the three can be confusing when you first look at it,
but I think the difference between "Aggregates" and the other two are pretty
self-explanatory when you start to actually use them. First of all "Aggregates"
aggregate unspecified amounts of data to a single value (such as median,
average, standard deviation, etc.) these are statistics tools. The other two
are a way of mapping(transforming/combining) one or more pieces of data into
one piece of data (this piece of data may be 0 or 1 dimensional, so a single
value or an array), these are regular mathematical tools like add, subtract,
multiply, etc. So you can use "Aggregate Mapping Operations/Expressions" and
"Field Mapping Operations" in the exact same way without thinking about it, the
only difference between the two is that one maps multiple lists into one list
and the other maps multiple values into one value. Actually after typing this
up I agree that the documentation of the feature could be significantly
improved, but I am not sure a syntactical difference between aggregates and the
other two are necessary since they don't share much functionality (really just
"sum" and "add"). Also the naming of "Aggregate Mapping Operations/Expressions"
and "Field Mapping Operations" should definitely be changed.
* Ok, I'm confused about this point. "Field Mapping Operations" are ValueSource
parsers... I used existing ones and added some of my own.
> Finalize interface and backport analytics component to 4x
> ---------------------------------------------------------
>
> Key: SOLR-5963
> URL: https://issues.apache.org/jira/browse/SOLR-5963
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.9, 5.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Attachments: SOLR-5963.patch, SOLR-5963.patch
>
>
> Now that we seem to have fixed up the test failures for trunk for the
> analytics component, we need to solidify the API and back-port it to 4x. For
> history, see SOLR-5302 and SOLR-5488.
> As far as I know, these are the merges that need to occur to do this (plus
> any that this JIRA brings up)
> svn merge -c 1543651 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545009 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545053 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545054 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545080 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545143 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545417 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545514 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1545650 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1546074 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1546263 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1559770 https://svn.apache.org/repos/asf/lucene/dev/trunk
> svn merge -c 1583636 https://svn.apache.org/repos/asf/lucene/dev/trunk
> The only remaining thing I think needs to be done is to solidify the
> interface, see comments from [[email protected]] on the two JIRAs mentioned,
> although SOLR-5488 is the most relevant one.
> [~sbower], [~houstonputman] and [[email protected]] might be particularly
> interested here.
> I really want to put this to bed, so if we can get agreement on this soon I
> can make it march.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
