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/10/31 11:14:58 UTC
[jira] [Resolved] (JENA-1249) ModelCom constuction triggers prefix
reading in TDB
[ https://issues.apache.org/jira/browse/JENA-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-1249.
---------------------------------
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.1.1
> ModelCom constuction triggers prefix reading in TDB
> ---------------------------------------------------
>
> Key: JENA-1249
> URL: https://issues.apache.org/jira/browse/JENA-1249
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Jena 3.1.1
>
> Attachments: ReportPerf.java
>
>
> For TDB, the Dataset-level wrapper is {{DatasetImpl}}. The model-level operations {{Dataset.getDefaultModel}} and {{Dataset.getNamedModel}} use a {{ModelCom}} to wrap the graph.
> The {{ModelCom}} construct also calls {{ModelCom.getPrefixMapping}} which in turn triggers the TDB graph level prefix mapping to be created.
> Due to JENA-81, the prefix map is read to the cache when the graph starts.
> Overall result - creating the model causes the prefix mappings to be read.
> We should avoid calling {{getPrefixMapping}} inside the {{ModelCom}} constructor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)