[ 
https://issues.apache.org/jira/browse/SOLR-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068931#comment-16068931
 ] 

Houston Putman commented on SOLR-10123:
---------------------------------------

{quote}(FWIW Houston, attaching patches showing your progress/attempts makes it 
easier for people to follow along with exactly what you're doing and offer 
meaningful ideas/suggestions){quote}
I understand, I'm pretty new to this so I don't really know how this is done. 
I've unsuccessfully tried to do the patch thing before, so I'll just make a 
pull request this time.

{quote}Personally i consider it a feature of Points fields{quote}

I completely agree, and I'm glad that this is finally possible. My comment was 
more to describe how the tests would be affected by it. However it does 
introduce an interesting problem where String & Boolean fields cannot have 
duplicate values, but Numeric fields can. But that is not a huge issue.

I have changed the tests to check whether point fields are being used and to 
test accordingly, and they now pass with the randomized numeric fields in the 
schemas.

The changes are in the following pull request: 
[https://github.com/apache/lucene-solr/pull/215]

{quote}shouldn't it be???{quote}
Yes, it should be tested. There are a lot of new features in this release and 
it is going to take a while to add unit tests for all of them.

> Analytics Component 2.0
> -----------------------
>
>                 Key: SOLR-10123
>                 URL: https://issues.apache.org/jira/browse/SOLR-10123
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Houston Putman
>              Labels: features
>         Attachments: SOLR-10123.patch, SOLR-10123.patch, SOLR-10123.patch
>
>
> A completely redesigned Analytics Component, introducing the following 
> features:
> * Support for distributed collections
> * New JSON request language, and response format that fits JSON better.
> * Faceting over mapping functions in addition to fields (Value Faceting)
> * PivotFaceting with ValueFacets
> * More advanced facet sorting
> * Support for PointField types
> * Expressions over multi-valued fields
> * New types of mapping functions
> ** Logical
> ** Conditional
> ** Comparison
> * Concurrent request execution
> * Custom user functions, defined within the request
> Fully backwards compatible with the orifinal Analytics Component with the 
> following exceptions:
> * All fields used must have doc-values enabled
> * Expression results can no longer be used when defining Range and Query 
> facets
> * The reverse(string) mapping function is no longer a native function



--
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

Reply via email to