You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/09/07 20:07:46 UTC
[jira] [Updated] (JENA-1023) Join library
[ https://issues.apache.org/jira/browse/JENA-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne updated JENA-1023:
--------------------------------
Labels: (was: ARQ)
> Join library
> ------------
>
> Key: JENA-1023
> URL: https://issues.apache.org/jira/browse/JENA-1023
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> This JIRA is for refactoring and adding more join algorithms into a join library.
> This is for joins between results from intermediate patterns, not joins that solve basic graph patterns.
> Normal use is a index join algorithm but it has some requirements about variable scope. ARQ falls back to a general join mechanism if the scoping requirements aren't met (this unusual).
> The general join code is not good. It should be, for example, a hash join if possible.
> Relation to JENA-266: There is hash-based anti-join code in {{org.apache.jena.sparql.engine.index}} in support of {{MINUS}}. This is not a proposal to combine that code into the join library. It is not immediately clear that code to cover all cases (inner join, left join and anti-join) at once is really a good idea if it leads to excessively complicated code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)