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 2016/01/30 22:46:39 UTC

[jira] [Resolved] (JENA-1083) Minor refactoring in TupleTables

     [ https://issues.apache.org/jira/browse/JENA-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne resolved JENA-1083.
---------------------------------
       Resolution: Done
    Fix Version/s: Jena 3.1.0

> Minor refactoring in TupleTables
> --------------------------------
>
>                 Key: JENA-1083
>                 URL: https://issues.apache.org/jira/browse/JENA-1083
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ
>            Reporter: A. Soroka
>            Assignee: A. Soroka
>            Priority: Minor
>             Fix For: Jena 3.1.0
>
>
> There are some minor refactorings available for TupleTable and its subtypes, particularly PMapTripleTable and PMapQuadTable that will clarify their use. Specifically, current impls of those abstract types have to override several methods for adding, removing, and finding tuples. In fact, the only information being added when those methods are overridden is conversion between canonical and internal tuple ordering. This refactoring is to provide methods that do that conversion and nothing else, which will make two methods the most that any implementation of those abstract classes will have to provide.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)