Thanks Vladimir. I have logged https://issues.apache.org/jira/browse/CALCITE-567 and https://issues.apache.org/jira/browse/CALCITE-568 for the points you raise. I agree they are not show-stoppers.
A Hive test run against the 1.0 RC had some cosmetic changes but also a few NPEs caused by https://issues.apache.org/jira/browse/CALCITE-566. Since this issue has a workaround I don't consider it a show-stopper. On Sat, Jan 24, 2015 at 1:10 PM, Vladimir Sitnikov <[email protected]> wrote: > I'm looking into dependencies list and I believe we'd better move > net.hydromatic:quidem:jar to a test scope. > > However I do not find how it blocks Calcite 1.0.0, so +1 from me. > > I've tested mat-calcite-plugin and it works with the suggested Calcite. > > It would be nice if pentaho-aggdesigner-algorithm could depend on > newer version of commons-logging so it would not result in > redistributing of servlet-api (even 1.1.1 use "provided" scope for > that). > > Here's the sub-set of compile dependencies of calcite-code: > > org.apache.calcite:calcite-core:jar:1.0.0-incubating > +- org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.3-jhyde:compile > | +- commons-lang:commons-lang:jar:2.4:compile > | \- commons-logging:commons-logging:jar:1.1:compile > | +- log4j:log4j:jar:1.2.12:compile > | +- logkit:logkit:jar:1.0.1:compile > | +- avalon-framework:avalon-framework:jar:4.1.3:compile > | \- javax.servlet:servlet-api:jar:2.3:compile > +- net.hydromatic:quidem:jar:0.2:compile > > Vladimir
