[
https://issues.apache.org/jira/browse/CLEREZZA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907232#action_12907232
]
Reto Bachmann-Gmür commented on CLEREZZA-286:
---------------------------------------------
Thanks manuel for your suggestions.
The file remains on disk as the cost of checking if in another triple there is
a reference to the same hash seems much higher than the waste of disk-space. we
could add a cleaning utility later that removes literal-files no longer
referenced in the undelying base graph.
I will implement the lazy reading feature you suggest.
I imagine adding a ValueTypedLiteral<T> object which extends TypedLiteral with
a getValue: T method, but we could also introduce a DataTypedLiteral which
extends ValueTypedLiteral<byte[]> and provides a getInputStream method.
> 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.
