On Sat, Apr 16, 2016 at 9:24 PM, Fabio Rinnone <[email protected]> wrote: > Il 15/04/2016 16:10, Roberto Franchini ha scritto: >> On Fri, Apr 15, 2016 at 12:29 PM, Fabio Rinnone >> <[email protected]> wrote: [cut]
> > Thank you, now it creates cluster, but my question is little different: > if I create for instance a class named "foo" and in my ETL loader I > define a new class named for instance "foocluster", when I launch ETL > (we assume that csv has 2000 rows), it loads 1000 rows into "foo" > cluster and the others 1000 into "foocluster", but I want that all 2000 > rows will loaded only into "foocluster". > > Is correct my assumption or probably don't I understand exactly the > meaning of role of clusters in OrientDB? First of all: docmentation http://orientdb.com/docs/last/Tutorial-Classes.html http://orientdb.com/docs/last/Tutorial-Clusters.html Now, ETL. If you configure ET to store on a given cluster, all the document loaded will be store in that cluster. So, you can load different data's partition on different clusters of the same class. Suppose to have 12 CSVs, one for each month. Each CSV contains contains invoices for a single month: invoices_01.csv contains invoices for January invoices_12.csv contains invoices for December It could be useful to "partion" Invoice class in 12 clusters, and load each csv on its own cluster. I hope this could clarify what's the purpose of Clusters. RF -- Best regards, Roberto Franchini OrientDB LTD - http://orientdb.com -- --- 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.
