es have a lot functions to handle JSON, besides
>>>> JSON_OBJECT or one or two other functions, seems none of its function
>> is
>>>> standardized.
>>>> https://dev.mysql.com/doc/refman/5.7/en/json-function-reference.html
>>>>
>>>> Pos
n.html
> > >
> > >
> > > While I think the scope could be self contained, if it is not suitable
> > for
> > > this activity do we want to put this into Calcite roadmap?
> > >
> > >
> > > Best,
> > >
> > > Chunhui
&g
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, at
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 ::= ( (|) | )
Var
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
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 any
son.html
> > >
> > >
> > > While I think the scope could be self contained, if it is not suitable
> > for
> > > this activity do we want to put this into Calcite roadmap?
> > >
> > >
> > > Best,
>
t; > this activity do we want to put this into Calcite roadmap?
> >
> >
> > Best,
> >
> > Chunhui
> >
> >
> > From: Julian Hyde
> > Sent: Monday, February 26, 2018 4:00:21 PM
> > To: dev
> > Subject
f it is not suitable for
> this activity do we want to put this into Calcite roadmap?
>
>
> Best,
>
> Chunhui
>
> ________
> From: Julian Hyde
> Sent: Monday, February 26, 2018 4:00:21 PM
> To: dev
> Subject: Re: Google Summer of Code 2018
>
> Yes.
>
>
> >
dmap?
Best,
Chunhui
From: Julian Hyde
Sent: Monday, February 26, 2018 4:00:21 PM
To: dev
Subject: Re: Google Summer of Code 2018
Yes.
> On Feb 26, 2018, at 2:32 PM, Michael Mior wrote:
>
> Thanks Julian! Would these be some good JIRAs to tag?
>
> https
Yes.
> On Feb 26, 2018, at 2:32 PM, Michael Mior wrote:
>
> Thanks Julian! Would these be some good JIRAs to tag?
>
> https://issues.apache.org/jira/browse/CALCITE-1737
> https://issues.apache.org/jira/browse/CALCITE-1861
> https://issues.apache.org/jira/browse/CALCITE-2031
>
> --
> Michael M
Thanks Julian! Would these be some good JIRAs to tag?
https://issues.apache.org/jira/browse/CALCITE-1737
https://issues.apache.org/jira/browse/CALCITE-1861
https://issues.apache.org/jira/browse/CALCITE-2031
--
Michael Mior
mm...@apache.org
2018-02-26 14:46 GMT-05:00 Julian Hyde :
> Here are two
Here are two areas that are self-contained and rewarding:
* Spatial functions
* Spark adapter
Julian
> On Feb 24, 2018, at 4:24 PM, Michael Mior wrote:
>
> You have probably seen that Apache was accepted as an organization for this
> year's GSoC. I thought I would see if anyone in the Calcite
13 matches
Mail list logo
