One of my clients uses MarR distribution & they don't use HBase. We tried using Kylin with MapR tables & it didn't work.
We could write & contribute but here's my question: It appears, the HBase key is this: <dim1>+<dim2>+....+<dimN> => values of measures for this combination, correct? Which means every query (except when all DIMs are grouped) would require scan, correct? How does Kylin do the HBase key lookup? I mean, if query requires grouping by only 2 DIMs, <dim1> & <dimN>, how is 'lookup' & 'scanning' handled? On Mon, Sep 12, 2016 at 6:28 PM, ShaoFeng Shi <[email protected]> wrote: > Cassandra isn't supported, as we don't see stronge need for that; if you > have the case, please share the scenario, thanks! > > Besides, we welcome contribution from the community, if you have the > willing to implement this, please also let us know. >
