[
https://issues.apache.org/jira/browse/SOLR-13010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697909#comment-16697909
]
Toke Eskildsen commented on SOLR-13010:
---------------------------------------
For the years 1-9999, the ISO-formatted {{String}} representations are
comparable in alphanumeric order. Instead of parsing to {{Instant}} all the
time, maybe do a quick check to see if the {{String}} representation of the
timestamp is within simple comparison-range and if so, use {{String}}
comparison and {{String}} for {{dateMax}}?
Caveat lector: I am not familiar with the streaming code at all, so the above
is very much guesswork.
> 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
