Hey Well not long since my last question which at least means I'm starting to work with OrientDB :)
For learning I thought I would look at migrating some of my RDBMS data across. Importing the films and users no problem with ETL. However, I wanted to then import the edges for actions the user has taken, such as 'watched' or 'owns'. I currently store this information in a table call film_entries, which looks something like so id|user_id|film_id|watched|owned|created 1, 1, 'gravity-2013', true, false, '2014-01-17 16:14' So from this I should easily be able to create an edge of 'watched', with an OUT being a lookup on User.Id , and the IN being a lookup on the Film.uuid which I have indexed and populated. However, firstly, ETL seems to require a vertex to create an edge. In this case, it would appear to be FilmEntries which is the source of the data, but I no longer need this. Secondly, I don't see a way for the ETL to create an Edge which has both an IN and OUT properties set at the same time. I have to create an IN, then create an OUT which seems redundant? I'm new to all of this, so forgive me if I'm missing something, but help now will mean less questions later! Of course the alternative is to write an import script in chosen language and not worry about ETL for now (just flat import the tables. created edges then delete) but that wouldn't be as neat :) Thanks Sky -- --- 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.
