[
https://issues.apache.org/jira/browse/CLEREZZA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902351#action_12902351
]
Reto Bachmann-Gmür commented on CLEREZZA-286:
---------------------------------------------
Starting to implement I think it could be as easy to make a TDB independent
solution as follows:
- LiteralExternalizingProvider is a TcProvider with a high prority that support
creation of MGraphs for URIs (graphname) that do not end with
"-externalizedliterals"
- When an MGraph is to be created it uses the TcManager to create an MGraph
with the requested name + the string "-externalizedliterals" so that another
provider will create this MGraph (referred to as baseMGraph)
- all read and write operations are directed to baseMGraph doing the
appropriate replacement of the literals
Issue:
- There's a circular reference between this Provider and the TcManager, but as
the references can be dynamic this shouldn't be an problem, the alternative
would be to reimplement significant parts of TcManager (which could have the
advantage of preventing duplicated locking and security checks)
> Inserting lager literals takes too long
> ---------------------------------------
>
> Key: CLEREZZA-286
> URL: https://issues.apache.org/jira/browse/CLEREZZA-286
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
>
> As binary resources are stored as literal values in the graph inserting
> literals of many MB is not a seldom usage scenario. Inserting such literals
> however take very long and thus require a very long write-lock on the graph
> (e.g. on my laptop 9 seconds when uploading a 40MB file with TDB and 3 second
> with Sesame)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
