I don't think there's specially efforts should to do for HBase v1.0 API if that API is compatibility with HBase v0.98.x. There's no special API Kylin depends on.
But I would like to call run some fully test with HBase v1.0 deployment to verify if there's any issue. If there's new API could benefit online/offline process, we should considering to support that. Thanks. Best Regards! --------------------- Luke Han 2015-05-23 0:57 GMT+08:00 Adunuthula, Seshu <[email protected]>: > We should also create a JIRA for Hbase 1.0 support. > > > > On 5/22/15, 9:47 AM, "Luke Han (JIRA)" <[email protected]> wrote: > > > > > [ > > > https://issues.apache.org/jira/browse/KYLIN-780?page=com.atlassian.jira.pl > >ugin.system.issuetabpanels:all-tabpanel ] > > > >Luke Han updated KYLIN-780: > >--------------------------- > > Fix Version/s: v0.7.2 > > > >> Upgrade Calcite to 1.0 > >> ---------------------- > >> > >> Key: KYLIN-780 > >> URL: https://issues.apache.org/jira/browse/KYLIN-780 > >> Project: Kylin > >> Issue Type: Bug > >> Affects Versions: v0.7.1 > >> Reporter: Julian Hyde > >> Fix For: v0.7.2 > >> > >> > >> There are significant API changes between Calcite 0.9.2 and 1.0. Read > >>the 1.0 release notes > >> > https://github.com/apache/incubator-calcite/blob/branch-1.3/doc/history.m > >>d#100-incubating--2015-01-31, and use the API mapping > >>https://issues.apache.org/jira/secure/attachment/12681620/mapping.txt if > >>you need to. > >> Kylin is currently on 0.9.1. Consider upgrading to 0.9.2 (the last > >>release with the old API) and getting that working before moving to the > >>renamed API. > > > > > > > >-- > >This message was sent by Atlassian JIRA > >(v6.3.4#6332) > >
