ject: Re: Stream SQL and Dynamic tables
Hi Radu,
yes, the clean-up timeout would need to be defined somewhere.
I would actually prefer to do that within the query, because the clean-up
timeout affects the result and hence the semantics of the computed result.
This could look for instance as
SELE
: Monday, January 30, 2017 9:07 PM
To: dev@flink.apache.org
Subject: Re: Stream SQL and Dynamic tables
Hi Radu,
yes, the clean-up timeout would need to be defined somewhere.
I would actually prefer to do that within the query, because the clean-up
timeout affects the result and hence the semantics of
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. If you receive this e-mail in error, please notify the sender
> > by phone or email immedia
)
TableEnvironment tbEnv =...
tbEnv.setCleanupTimeOut(100,TimeUnit.Minutes)
Table tb=
tb.setCleanupTimeOut(100,TimeUnit.Minutes)
-Original Message-
From: Fabian Hueske [mailto:fhue...@gmail.com]
Sent: Friday, January 27, 2017 9:41 PM
To: dev@flink.apache.org
Subject: Re: Stream SQL and Dynamic tables
. 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: Thursday, January 26, 2017 3:37 PM
> To: dev@flink.apache.org
> Subject:
bian Hueske [mailto:fhue...@gmail.com]
Sent: Thursday, January 26, 2017 3:37 PM
To: dev@flink.apache.org
Subject: Re: Stream SQL and Dynamic tables
Hi Radu,
the idea is to have dynamic tables as the common ground for Table API and SQL.
I don't think it is a good idea to implement and maintain
Hi Radu,
the idea is to have dynamic tables as the common ground for Table API and
SQL.
I don't think it is a good idea to implement and maintain 3 different
relational APIs with possibly varying semantics.
Actually, you can see the current status of the Table API / SQL on stream
as a subset of t
