Hi, Gaurav, The ibis::table layer is built on top of ibis::part and ibis::query. The class ibis::table offers a view of data that is somewhat closer to the SQL standard in that a query produces another table as the result.
Logically, a data table is split into any number of partitions. Each partition is represented by one physical directory and one ibis::part object. An ibis::query can only work with on ibis::part. The ibis::table layer works with an abstract data table without explicitly referring to the data partitions. You can image that you will have a lot more control over your data and operations if you use ibis::part and ibis::query. On the other hand, ibis::table interface might be a little easier to deal with. Hope this helps. John On 7/5/12 11:51 PM, Gaurav Agarwal wrote: > Hi John, > > I noticed that sql-like queries on the data could be executed using > the table interface and using query interface as well. Can you pls > explain the the differences between the two and how should one choose > between the two interfaces? > > thanks, > gaurav > _______________________________________________ > FastBit-users mailing list > [email protected] > https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users > _______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
