using oetl to import table from mysql

[Sam]

orientdb is saving integer field in source mysqldb tale as string during import using oetl...any idea why it is doing this and what can be done to prevent it?

[alessand...@gmail.com]

Hi Sam,

in the file .json you can define the type of your fields as follows

{ "csv": { "separator": ",", 

      "columns":[ "date:datetime", 

       "type:string", 

 "phone:string", 

 "old_token:string", 

 "new_token:string"] 

    } 

},

Regards,

Alessandro

[Saurabh Jain]

Alessandro...it is strange today it worked ok for one table....is there a bug in the etl library that sometimes it works and sometimes it does not?

Also..the table is imported but I am unable to see its properties in the studio....why is that so? I am able to see properties of other tables that are created in orientdb in the studio. How can I prevent that?

Thanks

Saurabh

--

---
You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/LHZeDtoYqxQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Giulia Brignoli]

Hi Sam.

you don't see any properties after the import, because etl process import the schema in modality schema-less. So this means that the properties do exist, but they aren't represented in the schema.

Regards, 

Giulia

[Saurabh Jain]

Can this be changed so that we get the properties also?

--

[Giulia Brignoli]

the only way I know to convert a schema from schema-less to schema-full is to add the properties in the class from Visual Studio. 

I honestly don't think it's a perfect solution, especially if you have many properties, but unfortunately I can't think of other solutions.

Regards,

Giulia

[Saurabh Jain]

Can you have this fixed in your next release. Issue is that the datatype should be matched. If it is bigint in source it should be long in orientdb, integer should be integer, varchar/string should be string and so on...right now it is buggy

also, the column names in source should come up as property names in orientdb...

--