[
https://issues.apache.org/jira/browse/CLEREZZA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904666#action_12904666
]
Manuel Innerhofer commented on CLEREZZA-286:
--------------------------------------------
I tried it out and here is what I found:
- The literals returned seem to be malformed. E.g. when I request a
infodiscobit the following exception occurs:
org.apache.clerezza.rdf.core.InvalidLiteralTypeException: Cannot create a class
[B from a literal of type <>
at
org.apache.clerezza.rdf.core.impl.SimpleLiteralFactory$ByteArrayConverter.createObject(SimpleLiteralFactory.java:91)
at
org.apache.clerezza.rdf.core.impl.SimpleLiteralFactory$ByteArrayConverter.createObject(SimpleLiteralFactory.java:78)
at
org.apache.clerezza.rdf.core.impl.SimpleLiteralFactory.createObject(SimpleLiteralFactory.java:287)
at
org.apache.clerezza.platform.content.InfoDiscobit.getData(InfoDiscobit.java:89)
The .rdf of this typed literal has no datatype and the literal itself starts
with "http://www.w3.org/2001/XMLSchema#base64Binary^^";
- I think the procedure to create a MGraph with externalized literals pretty
awkward. I know that it is provisional to do it the way you described (with
setting the startlevel etc.). But on the other hand assuming this bundle will
be delivered with the platform, how will I create a MGraph that shouldn't
externalize its literals? Do I have to stop/deactivate the
LiteralExternalizingProvider service, then create the MGraph that shouldn't
have externalized literals, then start LiteralExternalizingProvider again?
> 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.
