:twal...@apache.org]
> Sent: Monday, March 20, 2017 2:05 PM
> To: dev@flink.apache.org
> Subject: Re: FW: [DISCUSS] Table API / SQL indicators for event and
> processing time
>
> Yes, you are right. In the current design the user cannot assign
> timestamp and watermarks in a table pr
To: dev@flink.apache.org
Subject: Re: FW: [DISCUSS] Table API / SQL indicators for event and processing
time
Yes, you are right. In the current design the user cannot assign
timestamp and watermarks in a table program. Operators (such as windows)
might adapt the metatimestamp, if this is the
: Radu Tudoran
Subject: Re: [DISCUSS] Table API / SQL indicators for event and processing time
You are not bothering me, it is very interesting to compare the design
with real world use cases.
In your use case we would create table like: tEnv.toTable('date, 'time1,
'time2, 'data,
h 20, 2017 12:29 PM
To: Radu Tudoran
Subject: Re: [DISCUSS] Table API / SQL indicators for event and processing time
You are not bothering me, it is very interesting to compare the design
with real world use cases.
In your use case we would create table like: tEnv.toTable('date, 'time1,
>
> -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
> > > >>>>
> > > > > >>>>> we should make them system attributes; esp. to relate them
> to a
> > > > > >>>>>> corresponding table in case of multiple tables. Logically
> they
> > >
;>>> 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
>> >>> The table would also have another system attribute called "rowtime"
> >> >>> which would be used to indicate event time semantics.
> >> >>> These attributes would always be present in tables which are derived
> >> >>>
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
sons 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: Fabian Hueske [mailto:fhue...@gmail.com]
Sent: Tuesday, February 14, 2017 1:01 AM
To: dev@flink.apach
, HRB 56063,
> > > Geschäftsführer: Bo PENG, Wanzhou MENG, Lifang CHEN
> > > This e-mail and its attachments contain confidential information from
> > > HUAWEI, which is intended only for the person or entity whose address
> is
> > > listed above. Any use of the inform
ity 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 dissemination) by persons other than the intended recipient(s) is
> > prohibited
y phone or email immediately and delete it!
>
> -----Original Message-----
> From: Fabian Hueske [mailto:fhue...@gmail.com]
> Sent: Tuesday, February 14, 2017 1:01 AM
> To: dev@flink.apache.org
> Subject: [DISCUSS] Table API / SQL indicators for event and processing time
>
Fabian Hueske [mailto:fhue...@gmail.com]
Sent: Tuesday, February 14, 2017 1:01 AM
To: dev@flink.apache.org
Subject: [DISCUSS] Table API / SQL indicators for event and processing time
Hi,
I'd like to start an discussion about how Table API / SQL queries indicate
whether an operation is done in
Hi,
I'd like to start an discussion about how Table API / SQL queries indicate
whether an operation is done in event or processing time.
1) Why do we need to indicate the time mode?
We need to distinguish event time and processing time mode for operations
in queries in order to have the semantic
28 matches
Mail list logo
