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

ASF GitHub Bot commented on JENA-1083:
--------------------------------------

Github user ajs6f commented on a diff in the pull request:

    https://github.com/apache/jena/pull/120#discussion_r49192464
  
    --- Diff: 
jena-arq/src/main/java/org/apache/jena/sparql/core/mem/PMapQuadTable.java ---
    @@ -37,13 +39,29 @@
      * use.
      *
      */
    -public abstract class PMapQuadTable extends PMapTupleTable<FourTupleMap, 
Quad>implements QuadTable {
    +public class PMapQuadTable extends PMapTupleTable<FourTupleMap, Quad, 
Consumer4<Node>>implements QuadTable {
    +
    +
    +    private static class QuadTupleMap extends TupleMap {
    +
    +        private QuadTupleMap(final String mappedOrder) {
    +            super(mappedOrder, compileMapping("GSPO", mappedOrder));
    +        }
    +    }
    +
    --- End diff --
    
    It seems significantly clearer to me this way (the `static` methods just 
delegate to constructors, and it's clear from the outside that they must) but I 
have no problem doing it the other way. I'll add a commit "resetting" 
`TupleMap` and using `static`s later today.


> 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
>            Priority: Minor
>
> 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)

Reply via email to