[
https://issues.apache.org/jira/browse/JENA-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604765#comment-15604765
]
Andy Seaborne commented on JENA-1249:
-------------------------------------
Original report [email from users@ Nov
2016|https://lists.apache.org/thread.html/acd5c14d296d6acd2eeb55e7aa9a4727f50aa386bae80b38a8b7649f@%3Cdev.jena.apache.org%3E].
> 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
> 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)
