Re: Google Summer of Code 2018

Thanks Julian for the context. I have no insight on Sigma, unfortunately. I'm working toward adding such functionality to an Elixir Ecto based platform, and so will sketch something in due course - just concerned this may not be in time for a GSoC submission. Cheers, Mark. > On 28 Feb 2018,

[jira] [Created] (CALCITE-2196) Update codeGen of metadataHandler in JaninoRelMetadataProvider to include Class definition at begin of dynamic code.

jingzhang created CALCITE-2196: -- Summary: Update codeGen of metadataHandler in JaninoRelMetadataProvider to include Class definition at begin of dynamic code. Key: CALCITE-2196 URL:

Re: Google Summer of Code 2018

Good discussion. Some thoughts in no particular priority order: - I think we should also look at the SQL extensions that have been proposed in SQL++ [1] .. for instance the WHERE clause can contain a QuantifiedExpression such as QuantifiedExpression ::= ( (|) | )

Re: [DISCUSS] Towards Avatica 1.11.0

I just posted a pull request for https://issues.apache.org/jira/browse/CALCITE-2140: this is a small improvement for AvaticaStatement to add compatibility with DataGrip and other tools. It would be a nice to have for 1.11.0 Laurent On Tue, Feb 27, 2018 at 2:44 PM, F21

Re: Google Summer of Code 2018

Mark, Do you know if Sigma is built using Calcite? I’m totally in agreement about the power of SQL. You can create access-controlled views (or inject filters based on tenant id), give your end-users access to that layer, and you know that your users will get performance without being able to

Re: Google Summer of Code 2018

I'd like to suggest developing a convenient way to compose WHERE constraints on base queries, via the JSON api. Having a convenient way to inject rigorous application tenancy constraints would be huge boon for SaaS style applications. Calcite, with its JSON driver, could effectively enable

Re: [DISCUSS] Towards Avatica 1.11.0

Also would like to see https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-1951 worked on. Francis On 28/02/2018 9:34 AM, Julian Hyde wrote: OK, new thread just for the Avatica release. What’s left to do before 1.11? What can we accomplish before Monday? There are 20 open JIRA

Re: [DISCUSS] Towards Avatica 1.11.0

Do you guys think you can work on https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-2013 ? I tried bumping HSQLDB in the pom.xml a few months ago, but there were a few failing tests. Bumping HSQLDB will solve a bunch of issues I saw when testing avatica-go against avatica with

[DISCUSS] Towards Avatica 1.11.0

OK, new thread just for the Avatica release. What’s left to do before 1.11? What can we accomplish before Monday? There are 20 open JIRA cases tagged for 1.11:

Re: [DISCUSS] Towards Calcite 1.16.0

Thanks Julian. I did not reply to previous email, but plan sounded reasonable to me. I will be ready to have the first Calcite RC shortly after Avatica is released. -Jesús On 2/27/18, 11:49 AM, "Julian Hyde" wrote: Did we agree a target date for Calcite 1.16?

Re: [DISCUSS] Towards Calcite 1.16.0

Did we agree a target date for Calcite 1.16? In any case, I think we’d better do an Avatica release very soon. I volunteer to be release manager for Avatica. Can we aim for an RC of Avatica 1.11 on Monday (March 5)? Then, if all goes well, the first RC for Calcite 1.16 could be as early as

Re: Google Summer of Code 2018

While it would be great to have some movement forward on this, I think it seems too ambitious for a GSoC project. I am definitely looking forward to seeing this implemented though :) As for the issues I referenced earlier, I applied the GSoC label and below is a short link. Feel free to pass

Re: Google Summer of Code 2018

If we are to be ambitious, and to give someone a real challenge -- implement this approach for Calcite: Multi-objective Parametric Query Optimization https://cacm.acm.org/magazines/2017/10/221322-multi-objective-parametric-query-optimization/fulltext (I think Julian might have mentioned this once

Re: Google Summer of Code 2018

I would suggest creating a JIRA case to track this. It sounds like a basic implementation could be of reasonable scope for a GSoC project. -- Michael Mior mm...@apache.org 2018-02-26 19:09 GMT-05:00 Chunhui Shi : > What about "SQL support for JavaScript Object Notation (JSON)"? >

[jira] [Created] (CALCITE-2195) AggregateJoinTransposeRule fails to aggregate over unique column

Zhong Yu created CALCITE-2195: - Summary: AggregateJoinTransposeRule fails to aggregate over unique column Key: CALCITE-2195 URL: https://issues.apache.org/jira/browse/CALCITE-2195 Project: Calcite