Re: [orientdb] Re: OrientDB ETL tool

Thanks a lot indeed, Sir! On Thursday, 4 June 2015 15:31:22 UTC+1, l.garulli wrote: > > Hi James, > On last SNAPSHOTS (2.1-SNAPSHOT and 2.0.11-SNAPSHOT) the ETL can work with > parallel:true setting enabled to use the multicore better than in the > previous releases. > > Best Regards, > > Luca

[orientdb] Re: OrientDB ETL tool

Thank you very much indeed, Sir. On Friday, 29 May 2015 12:18:31 UTC+1, James Wang wrote: > > Hi All, > > I am new to OrientDB and trying to import data from a CSV file using the > ETL tool. > > Do I need to stop the OrientDB server firstly please? > Please help. > > Thanks a lot in advance > Jam

Re: [orientdb] Re: OrientDB ETL tool

Hi James, On last SNAPSHOTS (2.1-SNAPSHOT and 2.0.11-SNAPSHOT) the ETL can work with parallel:true setting enabled to use the multicore better than in the previous releases. Best Regards, Luca Garulli CEO at Orient Technologies LTD the Company behind OrientDB On 4 June 2015

Re: [orientdb] Re: OrientDB ETL tool

Hi James, no problem, your questions will be useful for many users ;-) If you need community suppor this is the best channel you can use. Thanks Luigi 2015-06-03 15:03 GMT+02:00 James Wang : > Just wanna to share: > > If run in stand alone (i.e. server.sh&), I managed to import 2500 vertice

[orientdb] Re: OrientDB ETL tool

Just wanna to share: If run in stand alone (i.e. server.sh&), I managed to import 2500 vertices per seconds - 12 times quicker than running in the distributed mode (dserver.sh&) Great. :-D On Friday, 29 May 2015 12:18:31 UTC+1, James Wang wrote: > > Hi All, > > I am new to OrientDB and trying

[orientdb] Re: OrientDB ETL tool

Thanks a lot. Tried to contact you via email (so as not to disturb others who may find my questions are not relevant or too simply) On Friday, 29 May 2015 12:18:31 UTC+1, James Wang wrote: > > Hi All, > > I am new to OrientDB and trying to import data from a CSV file using the > ETL tool. > >

Re: [orientdb] Re: OrientDB ETL tool

Hi James, there is a lot of improvement in the roadmap of OETL, we know that right now it is not optimized. If you are doing a one-shot import I suggest you to go with embedded and after that start the server. If you need very high performance you should consider Java API or OGraphBatchInsert (fo

[orientdb] Re: OrientDB ETL tool

Thanks, Luigi. More questions: is it possible to speed up OETL speed please? In remote mode, I can only import about 200 vertices per second Thanks a lot in advance On Friday, 29 May 2015 12:18:31 UTC+1, James Wang wrote: > > Hi All, > > I am new to OrientDB and trying to import data from a C

Re: [orientdb] Re: OrientDB ETL tool

Hi James, graph and document db internally are exactly the same, the only difference is the presence of V and E classes (this may be the reason of your failing ETL). I suggest you to go with that configuration and then, if you want, you can use your db as a normal document db. Luigi 2015-06-01

[orientdb] Re: OrientDB ETL tool

Hi All, If I change dbType=graph in the custoemr.json, I managed to import CSV file New question: can I import CSV file to a document database? If not ETL, is there another tool please? Thanks a lot James On Friday, 29 May 2015 12:18:31 UTC+1, James Wang wrote: > > Hi All, > > I am new to Or

[orientdb] Re: OrientDB ETL tool

Hi Luigi, Thanks a lot for your advice. I used plocal (not remote). Retied with the server being stopped. However, I had new errors: OrientDB etl v.2.0.8 (build @BUILD@) www.orientechnologies.com BEGIN ETL PROCESSOR Error in Pipeline execution: java.lang.NullPointerException java.lang.NullPoi