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 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 for 
> some examples. Or even post yours here?
>
> Am Montag, 20. Oktober 2014 12:36:57 UTC+2 schrieb Bojan Vukotić:
>>
>>
>> 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 :( How to improve this? 
>>
>>
>>
>> On Monday, 20 October 2014 12:16:08 UTC+2, Curtis Mosters wrote:
>>>
>>> Well you have several ways. Do you want to do it with JAVA oder the ETL 
>>> plugin?
>>>
>>> In any case I think it should be
>>>
>>> Vertices: Author, Book
>>> Edge: WROTE
>>>
>>> WDYT?
>>>
>>> Am Montag, 20. Oktober 2014 10:51:03 UTC+2 schrieb Bojan Vukotić:
>>>>
>>>> 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 books.
>>>>
>>>> Tables:
>>>>
>>>> Book {
>>>>        book_id
>>>>        book_name, 
>>>>         ....
>>>> }
>>>>
>>>> Author {
>>>>       author_id,
>>>>       author_name, 
>>>>       ......
>>>> }
>>>>
>>>>
>>>> Author_on_Book {
>>>>        ab_id,
>>>>        book_id,
>>>>        author_id,
>>>>        description // describes what this author did on this book 
>>>> }
>>>>
>>>> How to migrate this case? Should "Author_on_Book" be migrated as a 
>>>> vertex or edge? How to write scripts in this case? (in real life we could 
>>>> have even more foreign keys in "Author_on_Book" table )
>>>>
>>>>
>>>>

-- 

--- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to