Hello Lvc@,
Can you please be more specific on that approach?
I'm trying to do exactly (at least I think so, I'm a newbie:)) this.
I want OrientDB to find the routes between airports, basing on the flight
information - even if there's no direct flight (to find the route with
connections).
Regarding this slow import when doing it from code - I found how to improve
it (maybe ETL thread is not the right place to describe it)
My looked like:
OrientGraphNoTx graph = new OrientGraphNoTx(plocal:D:/orientdb/mydb);
// do importing of vertices - this part was ok and fast engough
// do
No comments on this?
Is there any configuration tweaks to be done to speed up things?
--
---
You received this message because you are subscribed to the Google Groups
OrientDB group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Do you use the Massive Insert intent ?
2014-10-24 15:43 GMT+02:00 BojanV bboojja...@gmail.com:
This answer is when I am working import from Javacode:
It differs - if my vertices are all in default class then around 50 edges
per second, If my vertices are in different classes then inserting
Yes it is correct
i have a similar importer. 50 edges per seconds are too low
seems strange
Can you try to use the OrientGraph and commit every 1000 entries?
you can use graph.begin()
and graph.commit()
to handle the transaction
2014-10-24 15:51 GMT+02:00 BojanV bboojja...@gmail.com:
If I use OrientGraphNoTx (as recommended) does begin/commit have sense at
all?
On Friday, 24 October 2014 16:12:08 UTC+2, Enrico Risa wrote:
Yes it is correct
i have a similar importer. 50 edges per seconds are too low
seems strange
Can you try to use the OrientGraph and commit every
Hi,
Try Tx and commit every 1k:
* tx: true,*
* batchCommit: 1000,*
Lvc@
On 24 October 2014 17:18, BojanV bboojja...@gmail.com wrote:
If I use OrientGraphNoTx (as recommended) does begin/commit have sense at
all?
On Friday, 24 October 2014 16:12:08 UTC+2, Enrico Risa wrote:
This is my code (I didn't use actually Book and Author tables, I used my
domain specific tables, but here I illustrated problem with these common
names to make it easier to understand).
This works, but my question is could this be done using just ETL without
any coding.
MapInteger,
I tried to use ETL as described here
http://www.orientechnologies.com/docs/last/orientdb-etl.wiki/Import-from-DBMS.html
I used slightly modified approach (I don't know is it a correct one). I
tried to import BookAuthor as vertex first (went fast and with no
problems), than I tried to import
Hi guys!
The whole discussion here is how to create edges from one table to another,
but what to do if we have more complex cases where we have connected 2 (or
even more) tables? Example, n:n relation: book and authors, book can have
one or more authors and author can work on one or more
I prefer do it with ETL, if it is possible, I would like to avoid
programming. If not, Java is also a good solution.
So, example how to do it in ETL? And regarding ETL, I was playing with it,
it imports vertices nicely, but when I want to import edges (100 000 of
them) it is extremely slow
Well I think it's way better to create a Java example. Then you understand
what is happening in the background. Otherwhise in my tests the ETL way had
the same speed, but these tests are 3-4 month old. I will redo them soon.
Did you take the example of ETL from OrientDB? Otherwhise look above
I took example from here
http://www.orientechnologies.com/docs/last/orientdb-etl.wiki/Import-from-DBMS.html
When can I find ETL/Java example?
On Monday, 20 October 2014 14:43:11 UTC+2, Curtis Mosters wrote:
Well I think it's way better to create a Java example. Then you understand
what is
I think I don't understand your issue:
First of all you import all Books. So you have all the data in there. Now
setting an index on the Book.ID.
After that the Authors are imported. They are matched with the ID of the
Book. I think in your case the Author matched with a Book is the same like
Well, that's exactly what I need (and what I already did). I thought maybe
that ETL has some API that we could use to make this easier (I used 'pure'
OrientDB API to implement this)
On Monday, 20 October 2014 15:15:27 UTC+2, Curtis Mosters wrote:
I think I don't understand your issue:
Is you code secret? I still don't understand the real issue you have, sorry.
Am Montag, 20. Oktober 2014 15:26:27 UTC+2 schrieb Bojan Vukotić:
Well, that's exactly what I need (and what I already did). I thought maybe
that ETL has some API that we could use to make this easier (I used 'pure'
@Bojan, How did you import edges? Can you share the code? It's hard to help
without any information.
Lvc@
On 20 October 2014 13:31, 'Curtis Mosters' via OrientDB
orient-database@googlegroups.com wrote:
Is you code secret? I still don't understand the real issue you have,
sorry.
Am Montag,
Hi Luca, it seem to work now.
But just tested with leightweight edges.
http://i.imgur.com/K18qTWm.png
Am Freitag, 26. September 2014 02:32:19 UTC+2 schrieb Lvc@:
Hey Curtis,
I've just fixed a bug on edge creation. Please could you retry with last
ETL version from github? (1.1-SNAPSHOT)
Hey Curtis,
I've just fixed a bug on edge creation. Please could you retry with last
ETL version from github? (1.1-SNAPSHOT)
Lvc@
On 28 August 2014 18:44, 'Curtis Mosters' via OrientDB
orient-database@googlegroups.com wrote:
D:\Eclipse LaTeX\DB -
Ops, sorry:
{ log : debug }
Lvc@
ᐧ
On 28 August 2014 10:14, 'Curtis Mosters' via OrientDB
orient-database@googlegroups.com wrote:
Just to make sure:
log: debug
or
log: true
?
Am Donnerstag, 28. August 2014 00:27:23 UTC+2 schrieb Lvc@:
Hi Curtis,
if you get last snapshot I've
Well not more infos in the command. Here again my updated JSON:
Author ETL:
{
config: {
log: debug
},
extractor : {
jdbc: { driver: com.mysql.jdbc.Driver,
url: jdbc:mysql://localhost/test,
userName: root,
userPassword: ,
Ahh I didn't use the latest snapshot, alright so I need to install ant. brb
with an update
Am Donnerstag, 28. August 2014 12:14:19 UTC+2 schrieb Curtis Mosters:
Well not more infos in the command. Here again my updated JSON:
Author ETL:
{
config: {
log: debug
},
extractor : {
Ok so I have now 2.0 and getting this here:
C:\Users\Mr. Kox\Desktop\orientdb-develop\releases\orientdb-community-2.0-
SNAPSH
OT\binoetl.bat backup\luca\Author.json
OrientDB etl v.2.0-SNAPSHOT (build @BUILD@) www.orientechnologies.com
Exception in thread main
Seems the database can't be created. Please check the db path, in case
there is a previous database drop it (from FS)
Lvc@
ᐧ
On 28 August 2014 14:03, 'Curtis Mosters' via OrientDB
orient-database@googlegroups.com wrote:
Ok so I have now 2.0 and getting this here:
C:\Users\Mr.
No the folder is completely empty.
But somehow I can't even create a database in the Studio.
http://i.imgur.com/Yacjoj7.png
401 Unauthorized.
Am Donnerstag, 28. August 2014 15:56:33 UTC+2 schrieb Lvc@:
Seems the database can't be created. Please check the db path, in case
there is a
Totally forgot that it is a complete other config. For sure. Now it's
working in the studio.
I again tried the ETL script but still having this here:
D:\Eclipse LaTeX\DB - orientdb\orientdb-community-2.0-SNAPSHOT\binoetl.bat
back
up\luca\Author.json
OrientDB etl v.2.0-SNAPSHOT (build @BUILD@)
D:\Eclipse LaTeX\DB - orientdb\orientdb-community-2.0-SNAPSHOT\binoetl.bat
back
up\luca\Author.json
OrientDB etl v.2.0-SNAPSHOT (build @BUILD@) www.orientechnologies.com
BEGIN ETL PROCESSOR
[orientdb] DEBUG - OrientDBLoader: created vertex class 'Author'
[orientdb] DEBUG - OrientDBLoader: created
Luca, could you also if you can't help me just give a statement. Just say
it does not work currently or you testing it or anything.
Just that I know this problem gets a solution because currently it's
unusable for Windows users =/
Thank you.
Am Dienstag, 26. August 2014 10:17:06 UTC+2 schrieb
Switching from Person to Author was just to test your Tutorial as exactly
as possible. I now added some logs. There you can see that there is no
warning but also no edge is created:
Person ETL:
{
config: {
verbose: true
},
extractor : {
jdbc: { driver: com.mysql.jdbc.Driver,
Hi Luca, well your example is just reading one table from MySQL. One table
with creating edges on it's entries. But in the usual cases that's not the
way how to import from a MySQL. Or maybe I just didn't understood that
example completely. But so far as I have seen it, you used one table from
Well there is an idea that might be easy to be implemented.
So the idea is to *auto-create* an edge. Let's take an example:
MySQL classes are:
- Person{id,name}
- Post{,person_id,title}
Now we also create such classes in OrientDB. Now we tell OrientDB if there
is INSERT INTO Person or
Hi Curtis,
getting your structure on MySQL:
- Person{id,name}
- Post{person_id,title}
You could configure 2 pipelines:
1. one with extraction of select * from Person
2. one with extraction of select * from Post
*Example for (1)*
{
config: {
verbose: true
},
extractor :
Sorry, create a new Edge's class: Wrote:
create class Wrote extends E
And put Wrote in the Edge's configuration.
Lvc@
ᐧ
On 25 August 2014 16:40, 'Curtis Mosters' via OrientDB
orient-database@googlegroups.com wrote:
Thanks Luca, I tried it out. The Person import works. But the more complex
No problem Luca, but still the same problem. Here are my JSON's. Just in
case I have something missing there. I braked it down to the things I
really need:
Person ETL:
{
config: {
verbose: true
},
extractor : {
jdbc: { driver: com.mysql.jdbc.Driver,
url:
What's the error?
ᐧ
On 25 August 2014 17:52, 'Curtis Mosters' via OrientDB
orient-database@googlegroups.com wrote:
No problem Luca, but still the same problem. Here are my JSON's. Just in
case I have something missing there. I braked it down to the things I
really need:
Person ETL:
{
Luca, I really don't know =/. Here is a picture, maybe more helpful:
http://i.imgur.com/f9QJvM8.png
Am Montag, 25. August 2014 18:07:01 UTC+2 schrieb Lvc@:
What's the error?
ᐧ
On 25 August 2014 17:52, 'Curtis Mosters' via OrientDB
orient-...@googlegroups.com javascript: wrote:
No
No problem,
the person id was null. Change the edge block to treat with a WARNING the
case:
{ edge: { class: Wrote, direction : in,
joinFieldName: person_id,
lookup:Person.id, unresolvedLinkAction:WARNING} }
Lvc@
ᐧ
On 25 August 2014 18:12, 'Curtis Mosters' via OrientDB
Well I tried some hours to get this running. Even studying
http://www.orientechnologies.com/docs/1.7.8/orientdb-etl.wiki/Transformer.html#edge
but nothing new to me.
Somehow the edges cannot be created with ETL. I'm using
*orientdb-etl-0.9.jar*. Should I maybe use another version?
Edit:
Hey so I have now some experiences with ETL. I think this is great for
import. That's why I want to improve the importing process now.
1. First of all is it possible to run several imports parallel(not with
several consoles) or if one is done start another instantly?
2. How do I
Hi Curtis,
ETL is very powerful and we're improving it everyday with users' feedback.
We want to let it to be final for 2.0, so we can bundle with it. By
the way Enterprise
Edition http://www.orientechnologies.com/orientdb-enterprise will have a
Web Interface to edit it, and in the future also to
This is a great example Luca, thanks first of all.
But could you additionally add information about the MySQL schema and do I
understand it correctly that you get the classes Person,Friend and an edge.
But where comes the friend data?
Am Donnerstag, 21. August 2014 13:25:47 UTC+2 schrieb Lvc@:
ᐧ
On 21 August 2014 14:45, 'Curtis Mosters' via OrientDB
orient-database@googlegroups.com wrote:
This is a great example Luca, thanks first of all.
But could you additionally add information about the MySQL schema and do I
understand it correctly that you get the classes Person,Friend and an
42 matches
Mail list logo
