[
https://issues.apache.org/jira/browse/JENA-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739737#comment-15739737
]
ASF GitHub Bot commented on JENA-1265:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/196
Yes - this makes overriding unnecessary. The second commit on this PR takes
it out of GraphTDB for the same reason.
Ideally, maybe, GraphBase should provide a safer set (no iterator remove,
no value indexing) and GraphMem / GraphMemBase add the specific capabilities.
Then the InfGraphs are probably inconsistent as their capabilities
partially rely on their base graph.
More evidence Capabilities are not used for real.
> GraphView : need to provide a safe set of capabilities, not the in-memory
> settings.
> -----------------------------------------------------------------------------------
>
> Key: JENA-1265
> URL: https://issues.apache.org/jira/browse/JENA-1265
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.1.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Jena 3.2.0
>
>
> GraphView provides a setting for Capabilities but that is derived from
> GraphBase, which is the in-memory settings. GraphView should provide settign
> - no iterator remove, no literal datatyping. Specific storage systems use of
> GraphView can override as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
