[
https://issues.apache.org/jira/browse/CLEREZZA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902466#action_12902466
]
Hasan commented on CLEREZZA-286:
--------------------------------
Reto,
ok. what I don't understand is how you would implement createMGraph in
LiteralExternalizingProvider. It will be invoked by TcManager when an MGraph is
to be created.
Something like this?
TcManager.createMGraph invokes LiteralExternalizingProvider.createMGraph
LiteralExternalizingProvider.createMGraph checks graphname ?
if it ends with -externalizedliterals, it throws unsupported exception
if it does not end with -externalizedliterals, it invokes
TcManager.createMGraph with appending -externalizedliterals to the graphname
Then TcManager.createMGraph invokes again
LiteralExternalizingProvider.createMGraph
OK. I think this should work, if the cycle does not pose a problem.
> 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.
