Timo Walther created FLINK-29267:
Summary: Support external type systems in DDL
Key: FLINK-29267
URL: https://issues.apache.org/jira/browse/FLINK-29267
Project: Flink
Issue Type: Improvement
).
Congratulations and welcome, Martijn!
Cheers,
Timo Walther
(On behalf of the Apache Flink PMC)
o configure by using 'DYNAMIC' at the metadata
column(or other better implementations).
[1]
https://nightlies.apache.org/flink/flink-docs-release-1.15/zh/docs/connectors/table/formats/debezium/
Timo Walther 于2022年8月25日周四 21:07写道：
Hi Ran,
what would be the data type of this dynamic metadata
Hi Ran,
what would be the data type of this dynamic metadata column? The planner
and many parts of the stack will require a data type.
Personally, I feel connector developers can already have the same
functionality by declaring a metadata column as `MAP`.
This is what we expose already as
Timo Walther created FLINK-29035:
Summary: ExpressionReducer does not work with jar resources
Key: FLINK-29035
URL: https://issues.apache.org/jira/browse/FLINK-29035
Project: Flink
Issue
Congratulations and welcome to the committer team :-)
Regards,
Timo
On 18.08.22 07:19, Lijie Wang wrote:
Congratulations, Junhan!
Best,
Lijie
Leonard Xu 于2022年8月18日周四 11:31写道：
Congratulations, Junhan!
Best,
2022年8月18日 上午11:27，Zhipeng Zhang 写道：
Congratulations, Junhan!
Xintong Song
Congratulations and welcome to the committer team :-)
Regards,
Timo
On 17.08.22 12:50, Yuxin Tan wrote:
Congratulations, Lijie!
Best,
Yuxin
Guowei Ma 于2022年8月17日周三 18:42写道：
Congratulations, Lijie. Welcome on board~!
Best,
Guowei
On Wed, Aug 17, 2022 at 6:25 PM Zhu Zhu wrote:
Hi
Timo Walther created FLINK-29014:
Summary: Use setting instead of merging for pipeline.jars in
StreamExecutionEnvironment.configure
Key: FLINK-29014
URL: https://issues.apache.org/jira/browse/FLINK-29014
Thanks Danny.
I will merge FLINK-28861 in couple of minutes to master. I will open a
PR for 1.15 shortly. This issue is pretty tricky, we should add a
warning to 1.15.0 and 1.15.1 releases as it won't be easy to perform
stateful upgrades in between 1.15.x patch versions for pipelines that
Hi all,
let me add a few more words on this topic:
The @PublicEvolving interface is kind of a staging annotation for
@Public. We still need to be careful when to change classes with
@PublicEvolving annotation. Usually, it still involves a proper
deprecation process over 1-2 releases to give
+1 (binding)
Thanks,
Timo
On 23.05.22 03:53, Jingsong Li wrote:
+1
Best,
Jingsong
On Sat, May 21, 2022 at 12:23 AM Shqiprim Bunjaku
wrote:
+1 (non-binding)
Best,
Shqiprim Bunjaku
On Fri, May 20, 2022 at 5:56 PM Yufei Zhang wrote:
+1 (non-binding)
Best,
Yufei Zhang
On Fri, May 20,
+1 (binding)
Thanks for driving this!
Timo
On 19.05.22 08:44, Leonard Xu wrote:
Thanks Xuyang for driving this work.
+1(binding)
Best,
Leonard
2022年5月19日 上午10:46，Yun Tang 写道：
Thanks for driving, +1 (binding)
Best
Yun Tang
From: Jark Wu
Sent:
t rather than the script. Considering the API in the
FLIP is not as same as the initialization in the CLI, I think we can use
the configure_session? What do you think, Timo?
Best,
Shengkai
Timo Walther 于2022年5月16日周一 14:28写道：
Hi Shengkai, Hi Jark,
thanks for the additional explanation and the
+1 (binding)
Thanks,
Timo
On 17.05.22 20:44, Gyula Fóra wrote:
+1 (binding)
On Tue, 17 May 2022 at 19:52, Yufei Zhang wrote:
+1 (nonbinding)
On Tue, May 17, 2022 at 5:29 PM Márton Balassi
wrote:
+1 (binding)
On Tue, May 17, 2022 at 11:00 AM Jingsong Li
wrote:
Thank Xintong for
Hi Shengkai, Hi Jark,
thanks for the additional explanation and the update of the FLIP. This
will help us in the future for documenting our decisions. The arguments
why to include the Gateway into the main repo make a lot of sense to me.
Esp. also because both CLI and gateway need some
Hi Shengkai,
sorry for jumping in so late into the discussion. There was a lot going
on in the last 3 weeks. This FLIP is very important and it is great that
you tackle this topic which is planned since we started with the SQL Client.
The ML discussion is already quite long. It would be
I also think that a real-time channel is long overdue. The Flink
community in China has shown that such a platform can be useful for
improving the collaboration within the community. The DingTalk channel
of 10k+ users collectively helping each other is great to see. It could
also reduce the
Timo Walther created FLINK-27534:
Summary: Apply scalafmt to 1.15 branch
Key: FLINK-27534
URL: https://issues.apache.org/jira/browse/FLINK-27534
Project: Flink
Issue Type: Improvement
Hi everyone,
I would like to send out a final reminder. We have already received some
great submissions for FlinkForward San Francisco 2022. Nevertheless, we
decided to extend the deadline by another week to give people a second
chance to work on their abstracts and presentation ideas.
This
It took a bit longer than usual. But I'm sure the users will love this
release.
Big thanks to the release managers!
Timo
Am 05.05.22 um 10:45 schrieb Yuan Mei:
Great!
Thanks, Yun Gao, Till, and Joe for driving the release, and thanks to
everyone for making this release happen!
Best
Yuan
Hi everyone,
The 1.15 release is almost out. We should still discuss whether we want
to backport scalafmt to the release-1.15 branch. Currently, it is quite
cumbersome to backport fixes in the table planner.
It seems scalafmt has stabilized in master. Are you ok with backporting
the changes
Hi Godfrey,
I'm also strictly against maintaining a Calcite fork. We had similar
discussions during the merge of the Blink code base in the past and I'm
happy that we could prevent a fork until today. Let me elaborate a bit
on my strict opinion here:
1) Calcite does not offer bugfix
-1
We found a regression in one of the core SQL operations (i.e. CAST
string<->binary) [1]. It would be better to fix this immediately to
avoid confusion. Also, we can use the time to fix another small
regression where a PR is also almost ready [2]. Both should be merged in
the next hours.
Thanks for the great work Francesco!
This will improve the contributor productivity a lot and ease reviews.
This change was long overdue.
Regards,
Timo
Am 12.04.22 um 17:21 schrieb Francesco Guardiani:
Hi all,
The new scalafmt formatter has been merged. From now on, just using mvn
Timo Walther created FLINK-27208:
Summary: Update the documentation to configure the IDE with
scalafmt
Key: FLINK-27208
URL: https://issues.apache.org/jira/browse/FLINK-27208
Project: Flink
Hi Fred,
thanks for starting this discussion. I totally agree that this an issue
that the community should solve. It popped up before and is still
unsolved today. Great that you offer your help here. So let's clarify
the implementation details.
1) Global vs. Local solution
Is this a
. Please give me the permission if possible.
My Confluence user name is `paulin3280`, and the full name is `Paul Lam`.
I'm also copying in @Timo Walther and @Jark Wu
for their opinion on this.
Looking forward to your opinions @Timo @Jark :)
Best,
Paul Lam
2022年4月1日 18:10，Martijn Visser 写道：
Hi
Timo Walther created FLINK-26843:
Summary: Cleanup code around TableConfig/ReadableConfig
Key: FLINK-26843
URL: https://issues.apache.org/jira/browse/FLINK-26843
Project: Flink
Issue Type
Hi Ron,
thanks for opening this discussion and proposing a FLIP. This feature
has been requested multiple times before and it is definitely something
that the Flink community wants. However, we have to ensure that this
change fits into the overall architecture and doesn't break core
Hi Konstantin,
thank you for starting this discussion again. It is a pitty that we have
never implemented FLIP-60 because it was the result of long offline
discussions with a lot of people closer working on the documentation topic.
I think splitting the documentation into *Option 1:
pm PDT!
See you there!
Timo Walther
Program Committee Chair
PS: Regarding Covid-19 regulations, we are following the CDC guidelines
closely. As we near closer to the event, we will update our policy
accordingly.
Timo Walther created FLINK-26725:
Summary: Support the new type inference in Scala Table API
aggregate functions
Key: FLINK-26725
URL: https://issues.apache.org/jira/browse/FLINK-26725
Project: Flink
Timo Walther created FLINK-26712:
Summary: Metadata keys should not conflict with physical columns
Key: FLINK-26712
URL: https://issues.apache.org/jira/browse/FLINK-26712
Project: Flink
+1 (binding)
- I scanned the commit diff and affected files.
- I could not find major API changes or otherwise problematic changes.
- The biggest changes I could spot were around Kubernetes (see FLINK-20830).
Thanks for taking care of this Konstantin.
Timo
Am 02.03.22 um 10:04 schrieb Yun
Timo Walther created FLINK-26518:
Summary: Support the new type inference in Scala Table API table
functions
Key: FLINK-26518
URL: https://issues.apache.org/jira/browse/FLINK-26518
Project: Flink
Big +1
This will improve the contribution experience. Even though we stopped
adding more Scala code, it is still necessary from time to time.
Regards,
Timo
Am 02.03.22 um 09:29 schrieb 刘首维:
+1
I still remember my first pr. Lack of experience, I had to pay attention to Scala
code format
Timo Walther created FLINK-26467:
Summary: Compile RowDataToStringConverter lazily
Key: FLINK-26467
URL: https://issues.apache.org/jira/browse/FLINK-26467
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-26434:
Summary: Remove 'table.planner' table config option
Key: FLINK-26434
URL: https://issues.apache.org/jira/browse/FLINK-26434
Project: Flink
Issue Type: Sub
+1
Thanks for bringing up this discussion one more time Marios.
I strongly support enabling the new behavior in 1.15. It definitely has
implications on existing users, but as Seth said, thinking about the
upcoming upgrade story we need to make sure that at least the core/basic
operations are
Timo Walther created FLINK-26287:
Summary: Add convenient TableConfig.set
Key: FLINK-26287
URL: https://issues.apache.org/jira/browse/FLINK-26287
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-26283:
Summary: Harden AggregateCall serialization in JSON plan
Key: FLINK-26283
URL: https://issues.apache.org/jira/browse/FLINK-26283
Project: Flink
Issue Type
Timo Walther created FLINK-26278:
Summary: Add Expressions.col as a synonym for $
Key: FLINK-26278
URL: https://issues.apache.org/jira/browse/FLINK-26278
Project: Flink
Issue Type: Bug
Timo Walther created FLINK-26250:
Summary: Document the upgrade story
Key: FLINK-26250
URL: https://issues.apache.org/jira/browse/FLINK-26250
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-26132:
Summary: Always serialize anonymous table
Key: FLINK-26132
URL: https://issues.apache.org/jira/browse/FLINK-26132
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-26075:
Summary: Persist per-ExecNode configuration
Key: FLINK-26075
URL: https://issues.apache.org/jira/browse/FLINK-26075
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-26055:
Summary: Use new FlinkVersion enum for serde plans
Key: FLINK-26055
URL: https://issues.apache.org/jira/browse/FLINK-26055
Project: Flink
Issue Type: Sub
Timo Walther created FLINK-26044:
Summary: Properly declare internal UNNEST function
Key: FLINK-26044
URL: https://issues.apache.org/jira/browse/FLINK-26044
Project: Flink
Issue Type: Sub
Timo Walther created FLINK-25990:
Summary: Expose uid generator for DataStream/Transformation
providers
Key: FLINK-25990
URL: https://issues.apache.org/jira/browse/FLINK-25990
Project: Flink
Timo Walther created FLINK-25932:
Summary: Introduce ExecNodeContext.generateUid()
Key: FLINK-25932
URL: https://issues.apache.org/jira/browse/FLINK-25932
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-25870:
Summary: Introduce ContextResolvedFunction similar to
ContextResolvedTable
Key: FLINK-25870
URL: https://issues.apache.org/jira/browse/FLINK-25870
Project: Flink
Timo Walther created FLINK-25845:
Summary: Expose plan via SQL COMPILE / EXECUTE PLAN
Key: FLINK-25845
URL: https://issues.apache.org/jira/browse/FLINK-25845
Project: Flink
Issue Type: Sub
Timo Walther created FLINK-25844:
Summary: Expose plan via StatementSet.compilePlan
Key: FLINK-25844
URL: https://issues.apache.org/jira/browse/FLINK-25844
Project: Flink
Issue Type: Sub
Timo Walther created FLINK-25843:
Summary: Expose plan via
Table.compilePlan/TableEnvironment.fromPlan
Key: FLINK-25843
URL: https://issues.apache.org/jira/browse/FLINK-25843
Project: Flink
Timo Walther created FLINK-25841:
Summary: Expose plan via
TableEnvironment.compilePlanSql/executePlan
Key: FLINK-25841
URL: https://issues.apache.org/jira/browse/FLINK-25841
Project: Flink
Timo Walther created FLINK-25826:
Summary: Handle symbols at a central place with serializable format
Key: FLINK-25826
URL: https://issues.apache.org/jira/browse/FLINK-25826
Project: Flink
Timo Walther created FLINK-25805:
Summary: Use compact DataType serialization for default classes
instead of internal ones
Key: FLINK-25805
URL: https://issues.apache.org/jira/browse/FLINK-25805
Timo Walther created FLINK-25769:
Summary: Add internal functions and basic function versioning
Key: FLINK-25769
URL: https://issues.apache.org/jira/browse/FLINK-25769
Project: Flink
Issue
Thank you so much for taking care of this Thomas and Martijn! A patch
release was long overdue.
Regards,
Timo
On 20.01.22 13:01, Till Rohrmann wrote:
Thanks a lot for being our release manager Thomas and Martijn and to
everyone who contributed to this release :-)
Cheers,
Till
On Thu, Jan
+1 (binding)
Regards,
Timo
On 19.01.22 14:47, Martijn Visser wrote:
Hi everyone,
I'd like to start a vote on creating external repositories [1]. Since the
thread is fairly long, I've also previously summarised it [2].
The vote will be open for at least 72 hours unless there is an objection
+1 (binding)
I think this will speed up connector evolution and core development
experience.
Regards,
Timo
On 19.01.22 14:47, Martijn Visser wrote:
Hi everyone,
I'd like to start a vote on moving connectors from Flink to external
connector repositories [1].
The vote will be open for at
Timo Walther created FLINK-25699:
Summary: Use HashMap for MAP value constructors
Key: FLINK-25699
URL: https://issues.apache.org/jira/browse/FLINK-25699
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-25677:
Summary: Update ReplicateRows to the new type system
Key: FLINK-25677
URL: https://issues.apache.org/jira/browse/FLINK-25677
Project: Flink
Issue Type: Sub
out the upgrade shortcoming.
The transformation changes should also be fine. The same transformation
is returned. The type has changed but it is unlikely that user query the
output type of a sink?
Regards,
Timo
On 17.01.22 09:45, Timo Walther wrote:
I went through the commit diff and found
I went through the commit diff and found the following changes that
might cause issues in my opinion. Maybe it makes sense to take a second
look before I will cast my vote:
// change of transformations
https://github.com/apache/flink/commit/b7cd97b02d7f39b5190d27fbaf6e6287f127b9a9
// change
Timo Walther created FLINK-25659:
Summary: LogicalRelDataTypeConverterTest is flaky on Azure
Key: FLINK-25659
URL: https://issues.apache.org/jira/browse/FLINK-25659
Project: Flink
Issue Type
Timo Walther created FLINK-25609:
Summary: Avoid creating temporary tables for inline tables
Key: FLINK-25609
URL: https://issues.apache.org/jira/browse/FLINK-25609
Project: Flink
Issue Type
Hi everyone,
for the Scala-free planner effort we introduced a new
`flink-table-test-utils`. It is recommended that connectors, formats,
and catalogs use this module as a test dependency if table-common is not
enough.
We will fill this module with more test utilities that can also be used
+1 for the separate project
But maybe use `flink-storage` instead of `flink-store`?
I'm not a native speaker but store is defined as "A place where items
may be purchased.". It almost sounds like the `flink-packages` project.
Regards,
Timo
On 07.01.22 08:37, Jingsong Li wrote:
Hi
Timo Walther created FLINK-25525:
Summary: flink-examples-table is not runnable in the IDE
Key: FLINK-25525
URL: https://issues.apache.org/jira/browse/FLINK-25525
Project: Flink
Issue Type
Timo Walther created FLINK-25516:
Summary: Add catalog object compile/restore options
Key: FLINK-25516
URL: https://issues.apache.org/jira/browse/FLINK-25516
Project: Flink
Issue Type: Sub
Hi everyone,
The new module flink-table-planner-loader replaces
flink-table-planner_2.12 and avoids the need for a specific Scala
version in downstream projects. It is included in the Flink distribution
under /lib. For backwards compatibility, users can still swap it with
+1 for a separate repository. And also +1 for finding a good name.
`flink-warehouse` would be definitely a good marketing name but I agree
that we should not start marketing for code bases. Are we planning to
make this storage also available to DataStream API users? If not, I
would also vote
Timo Walther created FLINK-25487:
Summary: Improve exception when flink-table-runtime is not in
classpath
Key: FLINK-25487
URL: https://issues.apache.org/jira/browse/FLINK-25487
Project: Flink
Timo Walther created FLINK-25392:
Summary: Add new STATEMENT SET syntax
Key: FLINK-25392
URL: https://issues.apache.org/jira/browse/FLINK-25392
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-25391:
Summary: Updating existing table factories for mutable table
options
Key: FLINK-25391
URL: https://issues.apache.org/jira/browse/FLINK-25391
Project: Flink
Timo Walther created FLINK-25390:
Summary: Support mutable options in DynamicTableFactory
Key: FLINK-25390
URL: https://issues.apache.org/jira/browse/FLINK-25390
Project: Flink
Issue Type
Timo Walther created FLINK-25389:
Summary: Update JSON plan with new ExecNodeMetadata
Key: FLINK-25389
URL: https://issues.apache.org/jira/browse/FLINK-25389
Project: Flink
Issue Type: Sub
Timo Walther created FLINK-25388:
Summary: Add annotation to all StreamExec nodes
Key: FLINK-25388
URL: https://issues.apache.org/jira/browse/FLINK-25388
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-25387:
Summary: Introduce ExecNodeMetadata annotation and tooling
Key: FLINK-25387
URL: https://issues.apache.org/jira/browse/FLINK-25387
Project: Flink
Issue Type
Timo Walther created FLINK-25386:
Summary: Harden table serialization in JSON plan
Key: FLINK-25386
URL: https://issues.apache.org/jira/browse/FLINK-25386
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-25385:
Summary: Harden function serialization in JSON plan
Key: FLINK-25385
URL: https://issues.apache.org/jira/browse/FLINK-25385
Project: Flink
Issue Type: Sub
rote:
+1 (non-binding)
On Wed, Dec 15, 2021 at 11:22 AM godfrey he wrote:
+1 (binding)
Best,
Godfrey
Ingo Bürk 于2021年12月15日周三 16:19写道：
+1 (binding)
Thanks for driving this much needed feature!
On 14.12.21 17:45, Timo Walther wrote:
Hi everyone,
I'd like to start a vote on FLIP-190: Sup
Timo Walther created FLINK-25365:
Summary: Remove remaining references to planner from Python
Key: FLINK-25365
URL: https://issues.apache.org/jira/browse/FLINK-25365
Project: Flink
Issue
Timo Walther created FLINK-25364:
Summary: Don't generate code in open() methods of Python operators
Key: FLINK-25364
URL: https://issues.apache.org/jira/browse/FLINK-25364
Project: Flink
Timo Walther created FLINK-25363:
Summary: Replace LogicalWindow and related planner expressions
Key: FLINK-25363
URL: https://issues.apache.org/jira/browse/FLINK-25363
Project: Flink
Issue
Timo Walther created FLINK-25341:
Summary: Improve casting structured type to STRING
Key: FLINK-25341
URL: https://issues.apache.org/jira/browse/FLINK-25341
Project: Flink
Issue Type: Sub
Hi everyone,
I'd like to start a vote on FLIP-190: Support Version Upgrades for Table
API & SQL Programs [1] which has been discussed in this thread [2].
The vote will be open for at least 72 hours unless there is an objection
or not enough votes.
[1]
Timo,
+1 for the improvement.
Best,
Godfrey
Timo Walther 于2021年12月10日周五 20:37写道：
Hi Wenlong,
yes it will. Sorry for the confusion. This is a logical consequence of
the assumption:
The JSON plan contains no implementation details (i.e. no classes) and
is fully declarative.
I will add a remark
Hi all,
I don't think it is easy to integrate this kind of functionality in
SQL/Table API. The CEP library can be more powerful than
MATCH_RECOGNIZE. I haven't taken a look at the FLIP yet. But I would be
fine to leave Table API/SQL up for future work and a separate FLIP.
Regards,
Timo
On
for the explanation. I totally agree with what you said.
My actual question is: Will the version of an exec node be serialised in
the Json Plan? In my understanding, it is not in the former design. If it
is yes, my question is solved already.
Best,
Wenlong
On Fri, 10 Dec 2021 at 18:15, Timo Walther
sion changes to 1.17.*
Best,
Wenlong
On Thu, 9 Dec 2021 at 18:36, Timo Walther wrote:
Hi Jing and Godfrey,
I had another iteration over the document. There are two major changes:
1. Supported Flink Upgrade Versions
I got the feedback via various channels that a step size of one minor
should
raise errors when
failed. The only question is how do we solve it, given lots of
users
already relying on current
more tolerant behavior. Some violation of standard but
acceptable
behavior
doesn't deserve
a breaking change in Flink minor version IMO, i'm more
comfortable
to
fix
i
hanged.
I think we need a detail explanation about the annotations change story in
the java doc of `ExecNodeMetadata` class for all developers
(esp. those unfamiliar with this part).
Best,
Godfrey
Timo Walther 于2021年12月8日周三 下午4:57写道：
Hi Wenlong,
thanks for the feedback. Great that we reached
Timo Walther created FLINK-25230:
Summary: Harden type serialization in JSON plan
Key: FLINK-25230
URL: https://issues.apache.org/jira/browse/FLINK-25230
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-25221:
Summary: Allow global table options for all table connectors
Key: FLINK-25221
URL: https://issues.apache.org/jira/browse/FLINK-25221
Project: Flink
Issue
may be not so friendly if we just throw deserialization
failure.
On Tue, 7 Dec 2021 at 16:49, Timo Walther wrote:
Hi Wenlong,
> First, we add a newStateLayout because of some improvement in state, in
> order to keep compatibility we may still keep the old state for the
first
> vers
Timo Walther created FLINK-25217:
Summary: FLIP-190: Support Version Upgrades for Table API & SQL
Programs
Key: FLINK-25217
URL: https://issues.apache.org/jira/browse/FLINK-25217
Project: F
and clean
up the deprecated code. We still need to update the version, so that we can
verify that we are compatible with the plan after the first change, but not
compatible with the plan earlier.
Best,
Wenlong
On Mon, 6 Dec 2021 at 21:27, Timo Walther wrote:
Hi Godfrey,
> design
Timo Walther created FLINK-25199:
Summary: fromValues does not emit final MAX watermark
Key: FLINK-25199
URL: https://issues.apache.org/jira/browse/FLINK-25199
Project: Flink
Issue Type: Bug
+1 (binding)
Thanks,
Timo
On 06.12.21 17:28, David Morávek wrote:
+1 (non-binding)
On Mon, Dec 6, 2021 at 4:55 PM Ingo Bürk wrote:
+1 (non-binding)
Ingo
On Mon, Dec 6, 2021 at 4:44 PM Chesnay Schepler
wrote:
Hello,
after recent discussions on the dev
101 - 200 of 1349 matches
Mail list logo
