OrientDB ETL: Looking for efficient work-around for lack of edge: skipDuplicates option -


i tried transformation { "edge" : { "class":"my_edge","skipduplicates":true } }...then noticed documentation had in of version 2.2. (4 releases now!?)

i'm bit stuck on viable work-around. have single flat file i'm trying break out 5 different objects. (things have deal when data end users).

i'd hoped skipduplicates option on vertex by-pass remaining transforms, no such luck.

is there block or command work-around can use. don't think sql lookup work, since other edges batch not have been committed yet.

by way, i've noticed when tried hack edge index, ended in kind of infinite loop...

thanks assistance.

update example -i'm using 2.1.8

here's basics of configuration

    {          "transformers" : [               { "merge": { "joinfieldname":"document_id", "lookup":"article.document_id" } },               { "vertex": { "class": "article" , "skipduplicates":true } },               { "edge": { "class":"belongs_to", "skipduplicates":true, "direction":"out","joinfieldname": "journal_id", "lookup":"journal.journal_id", "unresolvedlinkaction":"create"} },              ...           ]      }    //and of course, i've listed classes , indexes within orientdb loader      "classes":[          { "name":"content", "extends":"v" },          { "name":"article", "extends":"content" },          { "name":"belongs_to", "extends":"e" }      ],      "indexes": [          {"class":"article", "fields":["document_id:string"], "type":"unique" }      ]


Comments

Popular posts from this blog

ruby - Trying to change last to "x"s to 23 -

jquery - Clone last and append item to closest class -

c - Unrecognised emulation mode: elf_i386 on MinGW32 -