[
https://issues.apache.org/jira/browse/OAK-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680234#comment-13680234
]
sakshi arora commented on OAK-862:
----------------------------------
Example:
select [process-name], count(*) from [nt:rdb] where [duration] >= 5 group by
[status] order by [process-name]
'order by' would be needed too along with 'group by'
"For "group by duration", it sounds like we also need support for user defined
functions, or at least date manipulation (get the year, year+month,
year+month+day of a timestamp)."
In my current scenario its not needed as its a hard millisec difference, but
its a good to have thing.
Data will range from tens of thousand to tens of million. But the aggregate
results, in current scenarios would not cross a few thousands.
> Aggregate queries
> -----------------
>
> Key: OAK-862
> URL: https://issues.apache.org/jira/browse/OAK-862
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: sakshi arora
>
> ‘Group by’ query to get count(frequency) for each uid(could be a no. or
> string). This will extend to 'group by' on multiple fields, with the usual
> predicates ('where' - already available).
> The use-case involves, frequency-based summary charts.
> As charts are mostly frequency based, e.g. on duration, on category, on
> date/month/time/year.
> The data collection could range from live data to the daily scheduled
> synchronization.
> Required efficiency: Queries should be pretty fast, as usual location of
> these charts is on dashboards (which are the home pages for most sites).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
