is ready?
>
> Are there any show case or howto use?
>
>
>
> -邮件原件-
> 发件人: ewenstep...@gmail.com [mailto:ewenstep...@gmail.com] 代表 Stephan Ewen
> 发送时间: 2016年3月29日 20:00
> 收件人: dev@flink.apache.org
> 主题: Re: 答复: Effort to add SQL / StreamSQL to Flink
>
So excited!! SQL on Flink is ready?
Are there any show case or howto use?
-邮件原件-
发件人: ewenstep...@gmail.com [mailto:ewenstep...@gmail.com] 代表 Stephan Ewen
发送时间: 2016年3月29日 20:00
收件人: dev@flink.apache.org
主题: Re: 答复: Effort to add SQL / StreamSQL to Flink
Cool stuff!
SQL coming up
Cool stuff!
SQL coming up next? ;-)
On Tue, Mar 29, 2016 at 1:39 PM, Maximilian Michels wrote:
> Yeah! I'm a little late to the party but exciting stuff! :)
>
> On Fri, Mar 18, 2016 at 3:15 PM, Vasiliki Kalavri <
> vasilikikala...@gmail.com
> > wrote:
>
> > Hi all,
> >
> > tableOnCalcite has b
Yeah! I'm a little late to the party but exciting stuff! :)
On Fri, Mar 18, 2016 at 3:15 PM, Vasiliki Kalavri wrote:
> Hi all,
>
> tableOnCalcite has been merged to master :)
>
> Cheers,
> -Vasia.
>
> On 17 March 2016 at 11:11, Fabian Hueske wrote:
>
> > Thanks for the initiative Vasia!
> > I w
Hi all,
tableOnCalcite has been merged to master :)
Cheers,
-Vasia.
On 17 March 2016 at 11:11, Fabian Hueske wrote:
> Thanks for the initiative Vasia!
> I went over the diff and didn't find anything crucial.
>
> I would like to do another pass over the tests though and improve the
> exceptions
Thanks for the initiative Vasia!
I went over the diff and didn't find anything crucial.
I would like to do another pass over the tests though and improve the
exceptions for invalid joins before merging.
Will open a PR later today.
2016-03-16 21:17 GMT+01:00 Vasiliki Kalavri :
> Yes, the current
Yes, the current state corresponds to Task 1. PR #1770 corresponds to Task
5. Task 6 should come right after :)
-V.
On 16 March 2016 at 20:35, Robert Metzger wrote:
> Cool, this is great news!
> So "Task 1" from the document [1] is done with the merge? And PR #1770 is
> going towards "Task 6".
Hello everyone,
We are happy to announce that the "tableOnCalcite" branch is finally ready
to be merged.
It essentially provides the existing functionality of the Table API, but
now the translation happens through Apache Calcite.
You can find the changes rebased on top of the current master in [1]
Cool, this is great news!
So "Task 1" from the document [1] is done with the merge? And PR #1770 is
going towards "Task 6".
I think good support for Stream SQL is a very interesting new feature for
Flink.
[1]
https://docs.google.com/document/d/1TLayJNOTBle_-m1rQfgA6Ouj1oYsfqRjPcp1h2TVqdI/edit#head
Hi everybody,
as previously announced, I pushed a feature branch called "tableOnCalcite"
to the Flink repository.
We will use this branch to work on FLINK-3221 and its sub-issues.
Cheers, Fabian
2016-01-11 18:29 GMT+01:00 Fabian Hueske :
> We haven't defined the StreamSQL syntax yet (and I thin
We haven't defined the StreamSQL syntax yet (and I think it will take some
time until we are at that point).
So we are quite flexible with both featurs.
Let's keep this opportunity in mind and coordinate when before making
decisions about CEP or StreamSQL.
Fabian
2016-01-11 17:29 GMT+01:00 Till
First of all, it's a great design document. Looking forward having stream
SQL in the foreseeable future :-)
I think it is a good idea to consolidate stream SQL and CEP in the long
run. CEP's additional features compared to SQL boil down to pattern
detection. Once we have this, it should be only a
Thanks for the feedback!
We will start the SQL effort with putting the existing (batch) Table API on
top of Apache Calcite.
>From there we continue to add streaming support for the Table API before we
put a StreamSQL interface on top.
Consolidating the efforts with the CEP library sounds like a g
I suggest refering to Esper EPL[1], which is a SQL-standard language extend to
offering a cluster of window, pattern matching. EPL can both support Streaming
SQL and CEP with one unified syntax.
[1]
http://www.espertech.com/esper/release-5.2.0/esper-reference/pdf/esper_reference.pdf
(Chapt
14 matches
Mail list logo