>
> -Original Message-
> From: Timo Walther [mailto:twal...@apache.org]
> Sent: Monday, March 20, 2017 10:08 AM
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] Table API / SQL indicators for event and processing
> time
>
> Hi everyone,
>
> for the last
ve SUM, MAX, MIN, AVG, COUNT implemented but I could test it
just
on
simple queries such as the one above. Is there any specific case
I
should
be looking at?
Regards,
Stefano
-Original Message-
From: jincheng sun [mailto:sunjincheng...@gmail.com]
Sent: Tuesday, February 28, 2017 12:26 PM
To
would be defined based on cardinality of elements.
-Original Message-
From: Timo Walther [mailto:twal...@apache.org]
Sent: Monday, March 20, 2017 10:08 AM
To: dev@flink.apache.org
Subject: Re: [DISCUSS] Table API / SQL indicators for event and processing time
Hi everyone,
for the la
simple queries such as the one above. Is there any specific case I
should
be looking at?
Regards,
Stefano
-Original Message-
From: jincheng sun [mailto:sunjincheng...@gmail.com]
Sent: Tuesday, February 28, 2017 12:26 PM
To: dev@flink.apache.org
Subject: Re: [DISCUSS] Table API / SQL indic
> > > > > >>>>>
> > > > > >>>>> The query joins two streaming tables. Table 1 is a streaming
> > > table
> > > > > >>>>> with amounts in a certain currency. Table 2 is a (slowly
> > > changing)
> > &
;>>> This is not possible with a parameterless scalar function.
> > > > >>>>>
> > > > >>>>> I'd like to comment on the concerns regarding the performance:
> > > > >>>>> In fact, the columns could be completel
c case I
should
be looking at?
Regards,
Stefano
-Original Message-----
From: jincheng sun [mailto:sunjincheng...@gmail.com]
Sent: Tuesday, February 28, 2017 12:26 PM
To: dev@flink.apache.org
Subject: Re: [DISCUSS] Table API / SQL indicators for event and
processing
time
Hi everyone, thanks
gt; >
> > > I have SUM, MAX, MIN, AVG, COUNT implemented but I could test it just
> on
> > > simple queries such as the one above. Is there any specific case I
> should
> > > be looking at?
> > >
> > > Regards,
> > > Stefano
> > &
gards,
> > Stefano
> >
> > -----Original Message-----
> > From: jincheng sun [mailto:sunjincheng...@gmail.com]
> > Sent: Tuesday, February 28, 2017 12:26 PM
> > To: dev@flink.apache.org
> > Subject: Re: [DISCUSS] Table API / SQL indicators for event and
> pr
be looking at?
>
> Regards,
> Stefano
>
> -Original Message-
> From: jincheng sun [mailto:sunjincheng...@gmail.com]
> Sent: Tuesday, February 28, 2017 12:26 PM
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] Table API / SQL indicators for event and processing
> ti
any specific case I should be looking
at?
Regards,
Stefano
-Original Message-
From: jincheng sun [mailto:sunjincheng...@gmail.com]
Sent: Tuesday, February 28, 2017 12:26 PM
To: dev@flink.apache.org
Subject: Re: [DISCUSS] Table API / SQL indicators for event and processing time
Hi
gt;>>> and rowTime() only as functions which in fact are to be used as
>>>>>>
>>>>> markers.
>>>
>>>> Having the value (even from special system attributes does not make
>>>>>>
>>>>> sense
>>>&g
Original Message-
From: Timo Walther [mailto:twal...@apache.org]
Sent: Wednesday, February 15, 2017 9:33 AM
To: dev@flink.apache.org
Subject: Re: [DISCUSS] Table API / SQL indicators for event and
processing time
Hi all,
at first I also thought that built-in functions (rowtime() and
p
T R&D Division
> > >>
> > >>
> > >> HUAWEI TECHNOLOGIES Duesseldorf GmbH
> > >> European Research Center
> > >> Riesstrasse 25, 80992 München
> > >>
> > >> E-mail: radu.tudo...@huawei.com
> > >> M
; >> HUAWEI TECHNOLOGIES Duesseldorf GmbH
> >> Hansaallee 205, 40549 Düsseldorf, Germany, www.huawei.com
> >> Registered Office: Düsseldorf, Register Court Düsseldorf, HRB 56063,
> >> Managing Director: Bo PENG, Wanzhou MENG, Lifang CHEN
> >> Sitz der Gesellsc
s contain confidential information from
>> HUAWEI, which is intended only for the person or entity whose address is
>> listed above. Any use of the information contained herein in any way
>> (including, but not limited to, total or partial disclosure, reproduction,
>> or dissem
osure, reproduction,
> or dissemination) by persons other than the intended recipient(s) is
> prohibited. If you receive this e-mail in error, please notify the sender
> by phone or email immediately and delete it!
>
> -----Original Message-
> From: Timo Walther [mailto:twal...@a
and
delete it!
-Original Message-
From: Timo Walther [mailto:twal...@apache.org]
Sent: Wednesday, February 15, 2017 9:33 AM
To: dev@flink.apache.org
Subject: Re: [DISCUSS] Table API / SQL indicators for event and processing time
Hi all,
at first I also thought that built-in functions
Hi all,
at first I also thought that built-in functions (rowtime() and
proctime()) are the easiest solution. However, I think to be
future-proof we should make them system attributes; esp. to relate them
to a corresponding table in case of multiple tables. Logically they are
attributes of eac
Hi all,
thanks for this thread.
@Fabian If I didn't miss the point, the main difference between the two
approaches is whether or not taking these time attributes as common table
fields that are directly available to users. Whatever, these time
attributes should be attached to records (right?), an
Hi,
Thanks for starting the discussion. I can see there are multiple trade-offs
in these two approaches. One question I have is that to which extent Flink
wants to open its APIs to allow users to access both processing and event
time.
Before we talk about joins, my understanding for the two appro
Hi,
It would as in the query I gave as an example before:
SELECT
a,
SUM(b) OVER (PARTITION BY c ORDER BY proctime ROWS BETWEEN 2
PRECEDING AND CURRENT ROW) AS sumB,
FROM myStream
Here "proctime" would be a system attribute of the table "myStream".
The table would also have another system att
Hi Fabian,
Thanks for starting the discussion. Before I give my thoughts on this can you
please give some examples of how would you see option of using "system
attributes"?
Do you use this when you register the stream as a table, do you use if when you
call an SQL query, do you use it when you
23 matches
Mail list logo
