Hi,
related with this thread, Rupert has pointed me a very interesting paper
that brings back the idea to have a triple store implementation on top
of a NoSQL database:
Rya: A Scalable RDF Triple Store for the Clouds
http://www.usna.edu/Users/cs/adina/research/Rya_CloudI2012.pdf
I don not find the tools available out there, but it is very well
described, fir in Marmotta (they use Sesame) and the numbers look
promising to at least explore this path too.
Cheers,
On 21/05/13 22:50, Raffaele Palmieri wrote:
Hi to all,
I would propose a little a change to architecture of Importer Service.
Actually for every triple there are single SQL commands invoked from
SailConnectionBase that persist triple informations on DB. That's probably
one of major causes of delay of import operation.
I thought a way to optimize that operation, building for example a csv,
tsv, or *sv file that the major part of RDBMS are able to import in an
optimized way.
For example, MySQL has Load Data Infile command, Postgresql has Copy
command, H2 has Insert into ... Select from Csvread.
I am checking if this modification is feasible; it surely will need a
specialization of sql dialect depending on used RDBMS.
What do you think about? would it have too much impacts?
Regards,
Raffaele.
--
Sergio Fernández
