+1 (binding)
Cheers, Fabian
Timo Walther schrieb am Mo., 15. Jan. 2024, 16:00:
> +1 (binding)
>
> Cheers,
> Timo
>
>
> On 09.01.24 10:58, xiangyu feng wrote:
> > +1 (non-binding)
> >
> > Regards,
> > Xiangyu Feng
> >
> > Danny Cranmer 于2024年1月9日周二 17:50写道：
> >
> >> +1 (binding)
> >>
> >>
Hi everyone,
Sorry for joining this discussion late.
Let me give some thought to two of the arguments raised in this thread.
Time functions are inherently non-determintistic:
--
This is of course true, but IMO it doesn't mean that the semantics of time
functions do not matter.
It makes a
Fabian Hueske created FLINK-20578:
-
Summary: Cannot create empty array using ARRAY[]
Key: FLINK-20578
URL: https://issues.apache.org/jira/browse/FLINK-20578
Project: Flink
Issue Type: Sub
Congrats Congxian!
Cheers, Fabian
Am Mo., 2. Nov. 2020 um 10:33 Uhr schrieb Yang Wang :
> Congratulations Congxian!
>
> Best,
> Yang
>
> Zhu Zhu 于2020年11月2日周一 下午5:14写道：
>
> > Congrats Congxian!
> >
> > Thanks,
> > Zhu
> >
> > Pengcheng Liu 于2020年11月2日周一 下午5:01写道：
> >
> > > Congratulations
Fabian Hueske created FLINK-19790:
-
Summary: Writing MAP to Kafka with JSON format
produces incorrect data.
Key: FLINK-19790
URL: https://issues.apache.org/jira/browse/FLINK-19790
Project: Flink
Congrats and welcome Zhu!
Best, Fabian
Am Mo., 5. Okt. 2020 um 14:33 Uhr schrieb Yun Gao
:
> Congratulations Zhu!
>
> Best,
> Yun--
> Sender:Arvid Heise
> Date:2020/10/05 15:53:01
> Recipient:dev
> Cc:
> Theme:Re: [ANNOUNCE] New
Fabian Hueske created FLINK-19398:
-
Summary: Hive connector fails with IllegalAccessError if submitted
as usercode
Key: FLINK-19398
URL: https://issues.apache.org/jira/browse/FLINK-19398
Project
Fabian Hueske created FLINK-19321:
-
Summary: CollectSinkFunction does not define serialVersionUID
Key: FLINK-19321
URL: https://issues.apache.org/jira/browse/FLINK-19321
Project: Flink
Issue
Congrats Arvid and welcome aboard!
Cheers,
Fabian
Am Di., 15. Sept. 2020 um 10:23 Uhr schrieb Paul Lam :
> Congrats, Arvid!
>
> Best,
> Paul Lam
>
> > 2020年9月15日 15:29，Jingsong Li 写道：
> >
> > Congratulations Arvid !
> >
> > Best,
> > Jingsong
> >
> > On Tue, Sep 15, 2020 at 3:27 PM Dawid
Congrats Igal and welcome aboard!
Cheers,
Fabian
Am Di., 15. Sept. 2020 um 10:22 Uhr schrieb David Anderson <
da...@alpinegizmo.com>:
> Congrats, Igal! Well deserved.
>
> David
>
> On Tue, Sep 15, 2020 at 10:14 AM Tzu-Li (Gordon) Tai
> wrote:
>
> > Hi all,
> >
> > It's great seeing many new
Leonard, Thanks for updating the FLIP!
+1 to the current version.
Thanks, Fabian
Am Mo., 24. Aug. 2020 um 17:56 Uhr schrieb Leonard Xu :
> Hi all,
>
> I would like to start the vote for FLIP-132 [1], which has been discussed
> and
> reached a consensus in the discussion thread [2].
>
> The
says:
>>>
>>> > *This additional table is referred to as the history table, while the
>>> main table that stores current (actual) row versions is referred to as the
>>> current table or simply as the temporal table. *
>>>
>>> Besides, SQL:2011
track its latest version, we called this kind of temporal table as
>> latest-only temporal table. The temporal table in lookup join can only
>> track its latest version and thus it's also a latest-only temporal table.
>>
>> Best
>> Leonard
>>
>> 在 2020年8月
Congrats David, well deserved!
Cheers,
Fabian
Am Mi., 19. Aug. 2020 um 11:05 Uhr schrieb Marta Paes Moreira <
ma...@ververica.com>:
> Congrats, David! Thanks for being the Flink Stack Overflow hawk (on top of
> everything else, of course)!
>
> Marta
>
> On Thu, Aug 13, 2020 at 5:26 AM Roc
Wiesman 写道：
>
> +1 to the updated design.
>
> I agree with Fabian that the naming of "temporal table without version" is
> a bit confusing but the actual semantics make sense to me. I think just
> saying its a Flink managed lookup join makes sense.
>
> Seth
>
> On
s
>> >> not mention this explictly. I think we can keep it as an internal
>> concept
>> >> but I just wanted to ask for clarification.
>> >>>>
>> >>>> Yes, I want to keep it as an internal concept, we have discussed that
>
Fabian Hueske created FLINK-18988:
-
Summary: Continuous query with LATERAL and LIMIT produces wrong
result
Key: FLINK-18988
URL: https://issues.apache.org/jira/browse/FLINK-18988
Project: Flink
Hi Leonard,
Thanks for this FLIP!
Looks good from my side.
Cheers, Fabian
Am Do., 30. Juli 2020 um 22:15 Uhr schrieb Seth Wiesman :
> Hi Leondard,
>
> Thank you for pushing this, I think the updated syntax looks really good
> and the semantics make sense to me.
>
> +1
>
> Seth
>
> On Wed, Jul
Fabian Hueske created FLINK-18704:
-
Summary: Support DECIMAL types in datagen Table source connector
Key: FLINK-18704
URL: https://issues.apache.org/jira/browse/FLINK-18704
Project: Flink
Fabian Hueske created FLINK-18683:
-
Summary: Support @DataTypeHint for TableFunction output types
Key: FLINK-18683
URL: https://issues.apache.org/jira/browse/FLINK-18683
Project: Flink
Issue
Fabian Hueske created FLINK-18673:
-
Summary: Calling ROW() in a UDF results in
UnsupportedOperationException
Key: FLINK-18673
URL: https://issues.apache.org/jira/browse/FLINK-18673
Project: Flink
Fabian Hueske created FLINK-18672:
-
Summary: Fix Scala code examples for UDF type inference annotations
Key: FLINK-18672
URL: https://issues.apache.org/jira/browse/FLINK-18672
Project: Flink
Fabian Hueske created FLINK-18657:
-
Summary: Change semantics of DESCRIBE SELECT statement
Key: FLINK-18657
URL: https://issues.apache.org/jira/browse/FLINK-18657
Project: Flink
Issue Type
Fabian Hueske created FLINK-18623:
-
Summary: CREATE TEMPORARY TABLE not documented
Key: FLINK-18623
URL: https://issues.apache.org/jira/browse/FLINK-18623
Project: Flink
Issue Type: Bug
Congrats Piotr!
Cheers, Fabian
Am Di., 7. Juli 2020 um 10:04 Uhr schrieb Marta Paes Moreira <
ma...@ververica.com>:
> Go Piotr! Congrats!
>
> On Tue, Jul 7, 2020 at 7:15 AM Biao Liu wrote:
>
> > Congrats Piotr! Well deserved!
> >
> > Thanks,
> > Biao /'bɪ.aʊ/
> >
> >
> >
> > On Tue, 7 Jul 2020
/docs.microsoft.com/en-us/sql/relational-databases/tables/temporal-tables?view=sql-server-ver15
> Best,
> Kurt
>
>
> On Tue, Jun 23, 2020 at 9:12 PM Fabian Hueske wrote:
>
> > Hi everyone,
> >
> > Every table with a primary key and an event-time attribute provides w
Hi everyone,
Every table with a primary key and an event-time attribute provides what is
needed for an event-time temporal table join.
I agree that, from a technical point of view, the TEMPORAL keyword is not
required.
I'm more sceptical about implicitly deriving the versioning information of
a
that can also be confusing for users. There is no additional
> >> helpful semantic in using START over BEGIN.
> >>
> >> 3) Instead, we should rather parameterize the block statament with
> >> `STATEMENT SET` and keep the END of the block simple (also similar to
> >> CASE .
Fabian Hueske created FLINK-18378:
-
Summary: CatalogManager checks for CatalogTableImpl instead of
CatalogTable
Key: FLINK-18378
URL: https://issues.apache.org/jira/browse/FLINK-18378
Project: Flink
Congrats Yu!
Cheers, Fabian
Am Mi., 17. Juni 2020 um 10:20 Uhr schrieb Till Rohrmann <
trohrm...@apache.org>:
> Congratulations Yu!
>
> Cheers,
> Till
>
> On Wed, Jun 17, 2020 at 7:53 AM Jingsong Li
> wrote:
>
> > Congratulations Yu, well deserved!
> >
> > Best,
> > Jingsong
> >
> > On Wed,
>
> https://www.sqlservertutorial.net/sql-server-stored-procedures/sql-server-begin-end/
> [3]: https://dev.mysql.com/doc/refman/8.0/en/begin-end.html
>
> On Mon, 15 Jun 2020 at 20:50, Fabian Hueske wrote:
>
> > Hi everyone,
> >
> > FLIP-84 [1] added the concept
The exception is thrown when the StreamGraph is translated to a JobGraph.
The translation logic has a switch. If checkpointing is enabled, the Java
code generated by the optimizer is directly compiled in the client (in
contrast to compiling it on the TaskManagers when the operators are
started).
Hi everyone,
FLIP-84 [1] added the concept of a "statement set" to group multiple INSERT
INTO statements (SQL or Table API) together. The statements in a statement
set are jointly optimized and executed as a single Flink job.
I would like to start a discussion about a SQL syntax to group
Fabian Hueske created FLINK-18298:
-
Summary: Rename TableResult headers of SHOW statements
Key: FLINK-18298
URL: https://issues.apache.org/jira/browse/FLINK-18298
Project: Flink
Issue Type
Congratulations Benchao!
Cheers, Fabian
Am Do., 11. Juni 2020 um 08:25 Uhr schrieb Rui Li :
> Congrats!
>
> On Thu, Jun 11, 2020 at 9:41 AM godfrey he wrote:
>
> > Congratulations, Benchao!
> >
> > Best,
> > Godfrey
> >
> > Yun Gao 于2020年6月11日周四 上午8:57写道：
> >
> > > Congratulations, Benchao!
>
Fabian Hueske created FLINK-17845:
-
Summary: Can't remove a table connector property with ALTER TABLE
Key: FLINK-17845
URL: https://issues.apache.org/jira/browse/FLINK-17845
Project: Flink
bugs because not all
> the developers will understand this easily.
> [1]
> https://docs.microsoft.com/en-us/sql/relational-databases/tables/temporal-tables?view=sql-server-ver15
>
> Best,
> Kurt
>
>
> On Sat, May 9, 2020 at 5:32 AM Fabian Hueske wrote:
>
>> I think we
Thanks Marta and congratulations!
Am Mo., 11. Mai 2020 um 14:55 Uhr schrieb Robert Metzger <
rmetz...@apache.org>:
> Awesome :)
> Thanks a lot for driving this Marta!
>
> Nice to see Flink (by virtue of having Apache as part of the name) so high
> on the list, with other good open source
Hi everyone,
I like the idea of having a place to collect material (blogs, talk
recordings, slides) on Flink.
As Robert said, we had this before and dropped it at some point because the
content became stale.
Also I feel we would need something more dynamic than a static website
(like
T
>> after.*
>> FROM my_binlog
>> CHANGELOG OPERATION BY op
>> UPDATE KEY BY (id);
>>
>> -- my_table will materialize the insert/delete/update changes
>> -- if we have 4 records in dbz that
>> -- a create for 1004
>> -- an update for 1004
>> -- a creat
ble (maybe is a view now) as
> > > temporal
> > > > (or history tracked).
> > > >
> > > > The first thing is also mentioned and discussed in FLIP-105 design
> > draft
> > > > [1] which proposed a syntax
> > > > to conver
+--+
>
> "Regarding to the watermark on nested columns", that's a good approach
> which can both support watermark on nested columns in the future and keep
> current table form.
>
> [1] https://www.w3schools.com/sql/sql_p
>> Jark Wu 于2020年4月30日周四 下午11:38写道：
>>
>>> Hi,
>>>
>>> I'm in favor of Fabian's proposal.
>>> First, watermark is not a column, but a metadata just like primary key,
>>> so
>>> shouldn't stand with columns.
>>> Second,
gt; true
>
> UNQ
>
> (NULL)
>
> f1.q2 AS (`f1.q2` - INTERVAL '3' SECOND)
>
> f2
>
> VARCHAR<256>
>
> true
>
> (NULL)
>
> NULL
>
> f3
>
> BIGINT
>
> false
>
> UNQ
>
> f0 + 1
>
>
> Personally, I like the second on
Hi Godfrey,
Thanks for starting this discussion!
In my mind, WATERMARK is a property (or constraint) of a field, just like
PRIMARY KEY.
Take this example from MySQL:
mysql> CREATE TABLE people (id INT NOT NULL, name VARCHAR(128) NOT NULL,
age INT, PRIMARY KEY (id));
Query OK, 0 rows affected
mats. TEMPORAL VIEW is flexible but will involve
> more SQL codes. I think
> we can support them both.
>
> Best,
> Jark
>
> [1]:
>
> https://docs.google.com/document/d/1onyIUUdWAHfr_Yd5nZOE7SOExBc6TiW5C4LiL5FrjtQ/edit#heading=h.sz656g8mb2wb
>
> On Fri, 17 Apr 2020 at 2
EM_TIME AS OF x` would only
> > work on processing time by a lookup into the external system or on
> > event-time by using the time semantics that the external system supports.
> >
> > Regarding retraction table with a primary key and a time-attribute:
> >
> > Th
Hi all,
First of all, I appologize for the text wall that's following... ;-)
A temporal table join joins an append-only table and a temporal table.
The question about how to represent a temporal table join boils down to two
questions:
1) How to represent a temporal table
2) How to specify the
Congrats Hequn!
Am Fr., 17. Apr. 2020 um 14:29 Uhr schrieb hufeih...@mails.ucas.ac.cn <
hufeih...@mails.ucas.ac.cn>:
> Congratulations , Hequn
>
> Best wish
>
>
> hufeih...@mails.ucas.ac.cn
> Congratulations, Hequn!
>
> Paul Lam 于2020年4月17日周五 下午3:02写道：
>
> > Congrats Hequn! Thanks a lot for
Congrats Seth! Well deserved :-)
Cheers, Fabian
Am Di., 7. Apr. 2020 um 10:09 Uhr schrieb Yangze Guo :
> Congratulations Seth!
>
> Best,
> Yangze Guo
>
> On Tue, Apr 7, 2020 at 4:07 PM Jiayi Liao wrote:
> >
> > >
> > > Congratulations Seth :)
> > >
> > >
>
Congrats everyone!
Cheers, Fabian
Am Mi., 1. Apr. 2020 um 18:26 Uhr schrieb Yun Tang :
> Congratulations to all of you!
>
> Best
> Yun Tang
>
> From: Yang Wang
> Sent: Wednesday, April 1, 2020 22:28
> To: dev
> Subject: Re: [ANNOUNCE] New Committers and PMC
Fabian Hueske created FLINK-16716:
-
Summary: Update Roadmap after Flink 1.10 release
Key: FLINK-16716
URL: https://issues.apache.org/jira/browse/FLINK-16716
Project: Flink
Issue Type: Bug
Fabian Hueske created FLINK-16540:
-
Summary: Fully specify bugfix version of Docker containers in
Flink Playground docker-compose.yaml files
Key: FLINK-16540
URL: https://issues.apache.org/jira/browse/FLINK-16540
Hi,
RE error handling:
I don't think it is a good idea to simply log invalid hints. This makes it
very hard for systems that integrate Flink to consume these errors.
I'm not saying we should throw an exception. We could also execute a query
with invalid hints but should have a mechanism to
Fabian Hueske created FLINK-16309:
-
Summary: ElasticSearch 7 connector is missing in SQL connector list
Key: FLINK-16309
URL: https://issues.apache.org/jira/browse/FLINK-16309
Project: Flink
Fabian Hueske created FLINK-16308:
-
Summary: SQL connector download links are broken
Key: FLINK-16308
URL: https://issues.apache.org/jira/browse/FLINK-16308
Project: Flink
Issue Type: Bug
Congrats Jingsong!
Cheers, Fabian
Am Fr., 21. Feb. 2020 um 17:49 Uhr schrieb Rong Rong :
> Congratulations Jingsong!!
>
> Cheers,
> Rong
>
> On Fri, Feb 21, 2020 at 8:45 AM Bowen Li wrote:
>
> > Congrats, Jingsong!
> >
> > On Fri, Feb 21, 2020 at 7:28 AM Till Rohrmann
> > wrote:
> >
> >>
Fr., 14. Feb. 2020 um 17:48 Uhr schrieb Fabian Hueske :
> Hi everyone,
>
> We announced the program of Flink Forward San Francisco 2020.
> The conference takes place at the Hyatt Regency in San Francisco from
> March 23rd to 25th.
>
> On the first day we offer four
Hi everyone,
We announced the program of Flink Forward San Francisco 2020.
The conference takes place at the Hyatt Regency in San Francisco from March
23rd to 25th.
On the first day we offer four training sessions [1]:
* Apache Flink Developer Training
* Apache Flink Runtime & Operations
Fabian Hueske created FLINK-16067:
-
Summary: Flink's CalciteParser swallows error position information
Key: FLINK-16067
URL: https://issues.apache.org/jira/browse/FLINK-16067
Project: Flink
Congrats team and a big thank you to the release managers!
Am Mi., 12. Feb. 2020 um 16:33 Uhr schrieb Timo Walther :
> Congratualations everyone! Great stuff :-)
>
> Regards,
> Timo
>
>
> On 12.02.20 16:05, Leonard Xu wrote:
> > Great news！
> > Thanks everyone involved !
> > Thanks Gary and Yu
Fabian Hueske created FLINK-15826:
-
Summary: Add renameFunction() to Catalog
Key: FLINK-15826
URL: https://issues.apache.org/jira/browse/FLINK-15826
Project: Flink
Issue Type: Improvement
Fabian Hueske created FLINK-15825:
-
Summary: Add renameDatabase() to Catalog
Key: FLINK-15825
URL: https://issues.apache.org/jira/browse/FLINK-15825
Project: Flink
Issue Type: Improvement
rick! Just kidding :), it was
> > mostly
> > > > > done by Patrick, all kudos to him.
> > > > > Just one question, we will be able to still be featured as an
> > official
> > > > > docker image in this case?
> > > > >
Hi everyone,
The registration for Flink Forward SF 2020 is open now!
Flink Forward San Francisco 2020 will take place from March 23rd to 25th.
The conference will start with one day of training and continue with two
days of keynotes and talks.
We would like to invite you to join the Apache Flink
+1
Am Di., 28. Jan. 2020 um 15:23 Uhr schrieb Yun Tang :
> +1 (non-binding)
>
> From: Stephan Ewen
> Sent: Tuesday, January 28, 2020 21:36
> To: dev ; patr...@ververica.com <
> patr...@ververica.com>
> Subject: Re: [VOTE] Integrate Flink Docker image publication
Congrats Yu!
Good to have you on board!
Cheers, Fabian
Am Do., 23. Jan. 2020 um 11:13 Uhr schrieb Piotr Nowojski <
pi...@ververica.com>:
> Congratulations! :)
>
> > On 23 Jan 2020, at 10:48, Tzu-Li (Gordon) Tai
> wrote:
> >
> > Congratulations :)
> >
> > On Thu, Jan 23, 2020, 5:07 PM Yadong
Hi everyone,
First of all, thank you very much Patrick for maintaining and publishing
the Flink Docker images so far and for starting this discussion!
I'm in favor of adding the Dockerfiles in a separate repository and not in
the main Flink repository.
I also think that it makes sense to first
Fabian Hueske created FLINK-15644:
-
Summary: Add support for SQL query validation
Key: FLINK-15644
URL: https://issues.apache.org/jira/browse/FLINK-15644
Project: Flink
Issue Type: New
Hi everyone,
We know some of you only came back from holidays last week.
To give you more time to submit a talk, we decided to extend the Call for
Presentations for Flink Forward San Francisco 2020 until Sunday January
19th.
The conference takes place on March 23-25 with two days of talks and
Hi all,
Yes, I agree. It would be good to have dedicated methods to check the
validity of SQL queries.
I would propose to have two validation methods:
1. syntactic and semantic validation of a SQL query, i.e., SQL keywords,
catalog information, types in expressions and functions, etc. This is a
Hi all,
First of all, Happy New Year to everyone!
Many of you probably didn't spent the holidays thinking a lot about Flink.
Now, however, is the right time to focus again and decide which talk(s) to
submit for Flink Forward San Francisco because the Call for Presentations
is closing this
Congrats Zhu Zhu and welcome on board!
Best, Fabian
Am Fr., 13. Dez. 2019 um 17:51 Uhr schrieb Till Rohrmann <
trohrm...@apache.org>:
> Hi everyone,
>
> I'm very happy to announce that Zhu Zhu accepted the offer of the Flink PMC
> to become a committer of the Flink project.
>
> Zhu Zhu has been
Hi all,
Flink Forward North America returns to San Francisco on March 23-25, 2020.
For the first time in North America, the conference will feature two days
of talks and one day of training.
We are happy to announce that the Call for Presentations is open!
If you'd like to give a talk and share
+1 from my side as well.
Am Mi., 30. Okt. 2019 um 04:51 Uhr schrieb Jingsong Li <
jingsongl...@gmail.com>:
> Thanks jark for reminding me.
> I will start a vote thread.
>
> On Wed, Oct 30, 2019 at 11:40 AM Jark Wu wrote:
>
> > Hi Jingsong,
> >
> > Do we need a formal vote? Or do we need to wait
+1 (binding)
Am Mo., 21. Okt. 2019 um 16:18 Uhr schrieb Thomas Weise :
> +1 (binding)
>
>
> On Mon, Oct 21, 2019 at 7:10 AM Timo Walther wrote:
>
> > +1 (binding)
> >
> > Thanks,
> > Timo
> >
> >
> > On 21.10.19 15:59, Till Rohrmann wrote:
> > > +1 (binding)
> > >
> > > Cheers,
> > > Till
> > >
Fabian Hueske created FLINK-14313:
-
Summary: Add Gojek to Chinese Powered By page
Key: FLINK-14313
URL: https://issues.apache.org/jira/browse/FLINK-14313
Project: Flink
Issue Type: Task
>> precedence and should be stable within the local session. Otherwise it
> >> could magically disappear while someone else is performing modifications
> >> in the catalog.
> >>
> >> Furthermore, this feature is very useful for prototyping as users can
Hi all,
Sorry for the late reply.
I think it might lead to confusing situations if temporary functions (or
any temporary db objects for that matter) are bound to the life cycle of an
(external) db/catalog.
Imaging a situation where you create a temp function in a db in an external
catalog and
Fabian Hueske created FLINK-14227:
-
Summary: Add Razorpay to Chinese Powered By page
Key: FLINK-14227
URL: https://issues.apache.org/jira/browse/FLINK-14227
Project: Flink
Issue Type: Task
Fabian Hueske created FLINK-14213:
-
Summary: Link from Flink website to Getting Started Overview page
Key: FLINK-14213
URL: https://issues.apache.org/jira/browse/FLINK-14213
Project: Flink
Hi,
I gave you the permissions for the wiki.
Thanks, Fabian
Am Mi., 25. Sept. 2019 um 05:04 Uhr schrieb Yadong Xie :
> Hi all
>
> I'm proposing to improve the Flink user experience in the Web UI and I have
> created a draft proposal doc.
>
> Could anyone grant the permission to convert the doc
Maybe it's a mix of pushing to the ASF repository and Github mirrors?
I'm only pushing to the ASF repositories (although not that frequently
anymore...).
Cheers, Fabian
Am Di., 24. Sept. 2019 um 10:50 Uhr schrieb Till Rohrmann <
trohrm...@apache.org>:
> Pushing directly to Github also works for
> > > >> #3：2(+1), 3(-1), 3(0) - net: -1
> > > > >>
> > > > >> Given the result, I'd like to change my vote for #2 from 0 to +1,
> to
> > > > make
> > > > >> it a stronger case with net +3.5. So th
Hi Forward,
I gave you the permissions.
Best, Fabian
Am So., 22. Sept. 2019 um 13:03 Uhr schrieb Forward Xu <
forwardxu...@gmail.com>:
> Hi devs,
>
> I'd like to create a page about the Support SQL 2016-2017 JSON functions in
> Flink SQL
> <
>
Hi Jark,
Thanks for the summary!
I like the proposal!
It makes it very clear that an event time attribute is an existing column
on which watermark metadata is defined whereas a processing time attribute
is a computed field.
I have one comment regarding the section on "Complex Watermark
Hi Terry,
I gave you permissions.
Thanks, Fabian
Am Do., 19. Sept. 2019 um 04:09 Uhr schrieb Terry Wang :
> Hi all,
>
> As communicated in an email thread, I'm proposing Flink SQL ddl
> enhancement. I have a draft design doc that I'd like to convert it to a
> FLIP. Thus, it would be great if
-in functions.
Fabian
Am Do., 19. Sept. 2019 um 11:52 Uhr schrieb Kurt Young :
> Hi Fabian,
>
> I think it's almost the same with #2 with different keyword:
>
> CREATE TEMPORARY BUILTIN FUNCTION xxx
>
> Best,
> Kurt
>
>
> On Thu, Sep 19, 2019 at 5:50 PM Fabian Hueske w
t much more explicit than the above command.
Sorry for bringing up a new option in the middle of the discussion, but as
I said, I think it has a bunch of benefits and I don't see major drawbacks
(maybe you do?).
What do you think?
Fabian
Am Do., 19. Sept. 2019 um 11:24 Uhr schrieb Fabian Hueske :
FLIP.
> > >
> > >
> > > > > > > Thanks for sharing the pulsar FLIP.
> > > > > > > Would you mind enabling comments/suggestions on the google doc
> > > link?
> > >
> > > Sorry, my bad, I've enabled comments for the doc.
>
Hi everyone,
I thought again about option #1 and something that I don't like is that the
resolved address of xyz is different in "CREATE FUNCTION xyz" and "CREATE
TEMPORARY FUNCTION xyz".
IMO, adding the keyword "TEMPORARY" should only change the lifecycle of the
function, but not where it is
y bad, I've enabled comments for the doc.
> Does it work for now?
>
> On Thu, Sep 19, 2019 at 4:07 PM Fabian Hueske wrote:
> >
> > +1 to what Stephan (and Thomas) said.
> >
> > Am Do., 19. Sept. 2019 um 09:54 Uhr schrieb Stephan Ewen <
> se...@apache.org>
+1 to what Stephan (and Thomas) said.
Am Do., 19. Sept. 2019 um 09:54 Uhr schrieb Stephan Ewen :
> Some quick thoughts on the connector contribution process. I basically
> reiterate here what Thomas mentioned in another thread about the Kinesis
> connector.
>
> For connectors, we should favor a
Fabian Hueske created FLINK-14117:
-
Summary: Translate changes on documentation index page to Chinese
Key: FLINK-14117
URL: https://issues.apache.org/jira/browse/FLINK-14117
Project: Flink
Fabian Hueske created FLINK-14116:
-
Summary: Translate changes on Getting Started Overview to Chinese
Key: FLINK-14116
URL: https://issues.apache.org/jira/browse/FLINK-14116
Project: Flink
Fabian Hueske created FLINK-14115:
-
Summary: Translate DataStream Code Walkthrough to Chinese
Key: FLINK-14115
URL: https://issues.apache.org/jira/browse/FLINK-14115
Project: Flink
Issue
I'm not sure what you are asking for.
"execution: min/max-idle-state-retention" are the entries in the
configuration file for the SQL CLI client to configure "idle state
retention time" as described in the link that you posted.
Btw. user question should be directed to the u...@flink.apache.org
Hi,
This can be set via the environment file.
Please have a look at the documentation [1] (see "execution:
min-idle-state-retention: " and "execution: max-idle-retention: " keys).
Fabian
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.9/dev/table/sqlClient.html#environment-files
bles, views). If not given explicitly the
> > current catalog & database would be used, both in the create statement or
> > when using the function.
> >
> > Point taken though your preference would be to support overriding
> built-in
> > functions.
> >
>
Hi,
A GROUP BY query on a streaming table requires that the result is
continuously updated.
Updates are propagated as a retraction stream (see
tEnv.toRetractStream(table, Row.class).print(); in your code).
A retraction stream encodes the type of the update as a boolean flag, the
"true" and
1 - 100 of 1245 matches
Mail list logo
