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

Joel Bernstein edited comment on SOLR-15132 at 2/3/21, 6:15 PM:
----------------------------------------------------------------

So it doesn't care about the previous timestamps returned by the facet.


was (Author: joel.bernstein):
So it doesn't care about the preview timestamp returned by the facet.

> Add window paramater to the nodes Streaming Expression
> ------------------------------------------------------
>
>                 Key: SOLR-15132
>                 URL: https://issues.apache.org/jira/browse/SOLR-15132
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: streaming expressions
>            Reporter: Joel Bernstein
>            Priority: Major
>
> The *nodes* Streaming Expression performs a breadth first graph traversal. 
> This ticket will add a *window* parameter to allow the nodes expression to 
> traverse the graph within a window of time. 
> To take advantage of this feature you must index the content with a String 
> field which is an ISO timestamp truncated at ten seconds. Then the *window* 
> parameter can be applied to walk the graph within a *window prior* to a 
> specific ten second window and perform aggregations. 
> Here is an example using Solr logs to answer the following question: 
> What types of log events occurred in the 30 second window prior to 10 second 
> windows with the most slow queries:
> {code}
> nodes(facet(logs, q="qtime_s:[5000 TO *]", buckets="time_ten_seconds", 
> rows="25"),
>       walk="time_ten_seconds->time_ten_seconds",
>       window="3",
>       gather="type_s",
>       count(*))
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to