[
https://issues.apache.org/jira/browse/CLEREZZA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599867#comment-13599867
]
Rupert Westenthaler commented on CLEREZZA-736:
----------------------------------------------
I would suggest to use the SPO model/dataset (getDefault**) of Jena TDB to
store the meta information (the "graphNameIndex"). If you create an own named
graph for such information users will be able to query them by using the
union-graph. If you use the "default" model/dataset the data should not be part
of the union graph. As the single TDB Dataset Provider does anyway not use the
default (SPO) model/dataset this seams to be the best solution.
> Create a scalable Jena TDB based TcProvider to support up to 100,000+ named
> graphs
> ----------------------------------------------------------------------------------
>
> Key: CLEREZZA-736
> URL: https://issues.apache.org/jira/browse/CLEREZZA-736
> Project: Clerezza
> Issue Type: Bug
> Components: storage
> Reporter: Minto van der Sluis
> Attachments: Performance test report.pdf,
> ScalableTdbSingleDatasetTcProvider.patch
>
>
> The current SingleTdbSingleDatasetTcProvider supports multiple named graphs.
> The current implementation however is not very scalable. See attached
> performance report.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
