Re: Making Calcite release 1.9

For sure, I will be on it On Wed, Aug 24, 2016 at 1:56 AM, Julian Hyde wrote: > Unfortunately, the release manager has to be a committer. There are > practical reasons (you need write access to several ASF systems) and legal > ones (you are making the release on behalf of

[jira] [Created] (CALCITE-1359) Document how users can log security issues against Calcite and Avatica

Julian Hyde created CALCITE-1359: Summary: Document how users can log security issues against Calcite and Avatica Key: CALCITE-1359 URL: https://issues.apache.org/jira/browse/CALCITE-1359 Project:

Re: scan(DataContext, java.util.List) gets strange node like 'CAST($1):....' for a varchar column

Is your problem related to https://issues.apache.org/jira/browse/CALCITE-1153 or https://issues.apache.org/jira/browse/CALCITE-1330? > On Aug 22, 2016, at 8:17 AM, bluejoe

Re: Making Calcite release 1.9

Unfortunately, the release manager has to be a committer. There are practical reasons (you need write access to several ASF systems) and legal ones (you are making the release on behalf of Apache). That said, I very much appreciate your offer to help. Could you help with the logistics? For

scan(DataContext, java.util.List) gets strange node like 'CAST($1):....' for a varchar column

Hi, Dear developers, I am working on a SQL engine based on Calcite. I defined a AbstractTable which provides a getRowType() method to tell its columns look like: NAME char, AGE integer Then I override the scan(DataContext, java.util.List) method to implement the searching function. When I sent

[jira] [Created] (CALCITE-1358) Push filters on time dimension to Druid

Jesus Camacho Rodriguez created CALCITE-1358: Summary: Push filters on time dimension to Druid Key: CALCITE-1358 URL: https://issues.apache.org/jira/browse/CALCITE-1358 Project: Calcite

Re: Bindable cache

Yes, a cache of PreparedStatement. I suppose that cache could be in Calcite but it’s better if it could be in your app server. See https://issues.apache.org/jira/browse/CALCITE-963 . Julian > On Aug 23, 2016, at 7:50 AM, Tajdar Siddiqui

[jira] [Created] (CALCITE-1357) Recognize Druid Timeseries and TopN queries in DruidQuery

Jesus Camacho Rodriguez created CALCITE-1357: Summary: Recognize Druid Timeseries and TopN queries in DruidQuery Key: CALCITE-1357 URL: https://issues.apache.org/jira/browse/CALCITE-1357

Making Calcite release 1.9

It’s time to start work on Calcite release 1.9, so we can hit the “end of August” target. Does this timeline (end of August) still work for everyone? Would anyone like to be release manager? Are there any issues that people would like to get into 1.9 (and are prepared to work on)? It should

Re: Transforming the parse tree using a Hook

Hooks are intended mainly for tracing/monitoring applications, i.e. read-only. If you want to modify the query preparation life cycle (parse, validate, optimize) then you should probably sub-class org.apache.calcite.prepare.Prepare to use a different parser. See Driver.createPrepareFactory.

[jira] [Created] (CALCITE-1355) Upgrade to protobuf-java 3.0.0 (stable)

Josh Elser created CALCITE-1355: --- Summary: Upgrade to protobuf-java 3.0.0 (stable) Key: CALCITE-1355 URL: https://issues.apache.org/jira/browse/CALCITE-1355 Project: Calcite Issue Type: Task

Re: Bindable cache

Thanx for your response. I was playing around with kylin 1.5.2.1/calcite 1.6.0.Yes, the queries are limited and similar (params differ based on the user executing this query). So the approach would be to use a PreparedStatement Cache ? From: Julian Hyde To: