Hi Alessandro
>> Am 15.06.2012 12:34, schrieb Rupert Westenthaler:
>>>
>>> I think this is because of http://markmail.org/message/iz4piguvglo466t7
>
>
> Off the top of my head, and given the type of exception that you received, I
> think Rupert is right. But to confirm that I need numbers. How many
> ontologies have you been trying to upload since first running Stanbol, and
> how large?
>
> Can you check the size of your TDB data directory? from the felix console
> you have to note the bundle number of the "Clerezza - SCB Jena TDB Storage
> Provider" bundle (let it be N).
Good News: I finished today my work on the Single Dataset TDB provider
for Clerezza so if you use the 0.6-incubating-SNAPSHOT version of the
"rdf.jena.tdb.storage" you should now get this provider as default.
Data will be stored in the {bundle-data-dir} (meaning under
/stanbol/filix{bundleId}/data/), but we could change that by adding a
configuration to the stanbol launcher that changes that to something
like "${sling.home}/triplestore/tdb". This instance would be than used
as default by all Stanbol Components (including the Contenthub and the
ClerezzaYard of the Entityhub).
You could also configure an own TDB instance for the use with Ontonet
and configure the directory to something like
"${sling.home}/ontonet/tdb". In this case you could also configure/use
the UNION graph (read-only RDF graph over all named graphs).
If you want to go for that you
1. will need to use a filter to correctly inject your TcProvider (e.g.
by filtering based on the configured union-graph-uri) and use the
TcProvider interface in favor of the TcManager.
2. make sure you configure a low service.ranking (e.g.
Ingerger.MIN_VALUE) so that the TcManager does not use your TcProvider
to create instances
3. make sure that the configuration is included in the Ontonet (e.g.
by adding a "o.a.s.ontologymanager.defaults" bundle similar to those
of the enhancer and the entityhub
Until a Clerezza release of the Jena TDB storage provider bundle is
available we could temporary add the SNAPSHOT repository to maven
repository list. Even that we can not make releases with SNAPSHOT
dependencies it should be no problem to have those within the trunk.
best
Rupert
--
| Rupert Westenthaler [email protected]
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
