ASF GitHub Bot commented on JENA-1507:

GitHub user afs opened a pull request:


    JENA-1507: Fixes for aggregates when no WHERE match.

    This includes the two commits of PR #381.
    Commit 8a64ffee are the actual functional changes for JENA-1507.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/afs/jena jena-1507_aggregates

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #382
commit eb3b9beda79d35347daea1925752306b4ef5911f
Author: Andy Seaborne <andy@...>
Date:   2018-03-13T13:59:35Z

    Remove test printing. Remove info warnings.

commit 459a2b88f5e9544e5ddcc9979914eb0dca14b0d7
Author: Andy Seaborne <andy@...>
Date:   2018-03-13T14:00:06Z


commit 8a64ffeef483df37bcbd313ada28104a945d2027
Author: Andy Seaborne <andy@...>
Date:   2018-03-13T15:21:29Z

    JENA-1507: No rows when no match if GROUP BY used


> GROUP BY and aggregates when there are no matching of the WHERE pattern.
> ------------------------------------------------------------------------
>                 Key: JENA-1507
>                 URL: https://issues.apache.org/jira/browse/JENA-1507
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: ARQ
>    Affects Versions: Jena 3.6.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Major
> There are two bugs in ARQs handling of grouping when there are no results in 
> the WHERE clause.
> When there is a GROUP BY, the outcome should be no rows. 
>  * JENA-1487
>  * [users list 
> discussion|https://lists.apache.org/thread.html/72c2045e639c589880619443beafec5be963733e0f9f0887e134d467@%3Cusers.jena.apache.org%3E]
> When there is no GROUP BY, no aggregates, and no pattern match, the result 
> should be one row of no columns; when there is no GROUP BY, the result is 
> always one row.  It returns zero rows (v3.6.0 and before).

This message was sent by Atlassian JIRA

Reply via email to