I find the proposal quite interesting: whatever improves the import
performance would be nice!
Personally I'm not an expert on RDBMS, so I registered MARMOTTA-245 for
checking if your proposal is actually feasible. Whenever you'll get your
committer rights over the git repository, fell free to open a topic
branch if you consider the changes may need more to actually be usable.
The remembers me, that you would have to take a look to our development
practices:
http://marmotta.incubator.apache.org/development.html
For the moment in Marmotta we are using a branching workflow, that is
currently still under discussion/development:
http://markmail.org/message/ki5n2ren5mkh57hb
All contributions on those aspects are also welcomed!
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
