[
https://issues.apache.org/jira/browse/RYA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973552#comment-15973552
]
ASF GitHub Bot commented on RYA-260:
------------------------------------
GitHub user kchilton2 opened a pull request:
https://github.com/apache/incubator-rya/pull/156
RYA-260 Fluo SPARQL Processing Aggregation Support
## Description
>What Changed?
Added Aggregation support to the Fluo PCJ application. It is a known
problem that the Accumulo PCJ Index does not properly handle aggregation output
exporting. That should be covered by a new ticket. Also fixed a bunch of
resource leaks and changed up how the Fluo integration tests were implemented
so that they use the Fluo recipe for Accumulo exporting integration tests.
### Links
[Jira](https://issues.apache.org/jira/browse/RYA-260)
### Checklist
- [ ] Code Review
- [ ] Squash Commits
#### People To Reivew
@meiercaleb
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kchilton2/incubator-rya RYA-260-fixed
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-rya/pull/156.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #156
----
commit 278f6d92fcfe1c68a388b8aa1fcd7ca2134bcfaa
Author: Kevin Chilton <kevin.chil...@parsons.com>
Date: 2017-04-07T19:57:57Z
RYA-260 Fluo PCJ application has had Aggregation support added to it. Also
fixed a bunch of resource leaks that were causing integration tests to fail.
----
> Add Aggregation support for Fluo/PCJ app
> ----------------------------------------
>
> Key: RYA-260
> URL: https://issues.apache.org/jira/browse/RYA-260
> Project: Rya
> Issue Type: New Feature
> Reporter: Andrew Smith
> Assignee: Kevin Chilton
>
> A user must be able to submit a PCJ query that contains the following
> aggregation functions from SPARQL:
> * Sum
> * Count
> * Average
> * Min
> * Max
> This task does not include any aggregations that appear within a GroupBy
> clause. We only need to support queries that have the aggregation within the
> SELECT section.
> For example, the following query should be processed:
> {code}
> SELECT (avg(?price) as ?averagePrice)
> {
> urn:BookA urn:price ?price.
> }
> {code}
> And the following query should not be processed because it requires a group
> by:
> {code}
> SELECT ?title (avg(?price) as ?averagePrice)
> {
> ?title urn:price ?price.
> }
> GROUP BY ?title
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
