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 2013/11/06 11:41:19 UTC

[jira] [Commented] (JENA-106) Merge joins in TDB

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

Andy Seaborne commented on JENA-106:
------------------------------------

[Email about plain literals => xsd:string, rdf:langString|http://mail-archives.apache.org/mod_mbox/jena-dev/201310.mbox/%3C525A8428.1050207%40apache.org%3E]

> Merge joins in TDB
> ------------------
>
>                 Key: JENA-106
>                 URL: https://issues.apache.org/jira/browse/JENA-106
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: TDB
>            Reporter: Paolo Castagna
>              Labels: gsoc2013, mentor, performance, scalability, tdb
>
> "TDB indexes do return predictably ordered results from a index access. Merge joins can be done and would be especially useful to apply to the first two triple patterns (later ones depend on whether the result of the first two come up in a useful order)." -- http://markmail.org/message/4gys5lidzbgwzxks
> OpExecutorTDB is the place to start looking into this (I think...).



--
This message was sent by Atlassian JIRA
(v6.1#6144)