[
https://issues.apache.org/jira/browse/SOLR-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697309#comment-16697309
]
Gus Heck commented on SOLR-13010:
---------------------------------
This works with the patch I am attaching, but I'm not exactly 100% thrilled
with this because I suspect it's rather expensive to be parsing date values for
large datasets, and would be happy for someone to point out if there was
already a way to get the time field to come back as an integer instead of a
string. Certainly one could possibly index it two ways and then use that, but
it's not always convenient to re-index one's data. But given that I have this
coded already, I'm putting it out here and will add docs/test up docs and add
it if no-one objects in a week or two since a slow option is better than no
option. Suggestions quite welcome...
> max rollup for dates
> --------------------
>
> Key: SOLR-13010
> URL: https://issues.apache.org/jira/browse/SOLR-13010
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: streaming expressions
> Affects Versions: master (8.0)
> Reporter: Gus Heck
> Priority: Minor
> Attachments: SOLR-13010.patch
>
>
> Sometimes it's useful to know the maximum or minimum value of a date field
> that's passing through a rollup() command. For example in the following
> expression, the effect would be to portray the freshness of the data for the
> bucket on which the counts have been generated.
> {code:java}
> rollup(search(activate2018-tra, q="racecar_id:*",
> fl="id,presented_date,racecar_id", sort="racecar_id
> asc",rows=99999),over=racecar_id, max(presented_date),count(*)){code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
