James, Thanks for the reply! I understand HBase has no query language per se, but if I was trying to create the most basic possible adapter for HBase, it seems like the most straightforward approach would be to expose HBase tables and implement scans as a possible query plan operator. This would require the user to specify a schema, but of course this needs to happen with Phoenix anyway.
That said, given that Phoenix does exist, the approach makes a lot of sense and obviously adds additional features. In general, I'm interested in incorporating the use of materialized views when querying databases such as Cassandra and HBase and exploring what needs to change from the relational world. If there's a way that this fits into the current plans for Phoenix + Calcite, I'd love to talk more. I'm still trying to wrap my head around both code bases. If there's any particular documentation you can point to that you think would be helpful, do let me know! Cheers, -- Michael Mior [email protected] 2016-01-20 16:37 GMT-05:00 James Taylor <[email protected]>: > Hi Michael, > We'd love for you to get involved on the Phoenix on Calcite work. I'd be > good to hear more on your thoughts about our implementation being "too > Phoenix-specific to enable the use of vanilla HBase". HBase has no query > language. We're basically leverage Calcite to do query optimization (at the > relational algebra level) over HBase. > Thanks, > James > > On Wed, Jan 20, 2016 at 1:32 PM, Michael Mior <[email protected]> wrote: > > > Hello Calcite devs! > > > > I'm a PhD student at the database group of the University of Waterloo in > > Ontario, Canada. My work has focused on schema optimization for NoSQL > > databases (specifically Cassandra for the time being). You can see a > piece > > of my recent work at the link below where I developed an automated tool > to > > design efficient schemas for Cassandra based on a description of > > application workloads. > > > > > > > https://www.researchgate.net/publication/289372760_NoSE_Schema_Design_for_NoSQL_Applications > > > > I'm really interested on getting involved in Calcite and I have two main > > questions > > > > 1) What is the status of lattices in Calcite? I read the documentation ( > > https://calcite.apache.org/docs/lattice.html) but it's unclear what's > been > > implemented or how it works. Specifically, the documentation seems to > > suggest that Calcite will automatically select tiles to create. Are there > > any examples of using lattices I can look at? > > > > 2) Is there any work being done on an adapter for Cassandra or HBase? > This > > is something I would be interested in contributing to. I know the Phoenix > > folks are working on integrating with Calcite, but it looks like their > > implementation is too Phoenix-specific to enable the use of vanilla > HBase. > > > > Thanks! > > > > Cheers, > > -- > > Michael Mior > > [email protected] > > http://michael.mior.ca/ > > >
