Timo Walther created FLINK-38201:
Summary: SinkUpsertMaterializer should not be inserted for retract
sinks
Key: FLINK-38201
URL: https://issues.apache.org/jira/browse/FLINK-38201
Project: Flink
+1 (binding)
Cheers,
Timo
On 04.08.25 14:03, Jacky Lau wrote:
+1 (non-binding)
Best regards,
Jacky
Hao Li 于2025年8月2日周六 08:47写道：
+1 (non-binding)
Thanks,
Hao
On Fri, Aug 1, 2025 at 5:33 PM Sergey Nuyanzin
wrote:
+1 (binding)
On Fri, Aug 1, 2025 at 5:18 PM Ramin Gharib
wrote:
Hi Da
+1 (binding)
Thanks,
Timo
On 01.08.25 07:05, Lincoln Lee wrote:
+1 (binding)
Best,
Lincoln Lee
Leonard Xu 于2025年8月1日周五 10:07写道：
+1 (binding)
Best,
Leonard
2025 8月 1 07:38，Mayank Juneja 写道：
+1 (non binding)
*Mayank Juneja*
Product Manager | Data Streaming and AI
On Thu, Jul 31, 2
Factory? I think connection is
like
CatalogTable. It should hold the basic information and all
information in
the connection should be stored into secret store.
Best,
Shengkai
Timo Walther 于2025年7月22日周二 22:04写道：
Hi Mayank,
Thanks for updating the FLIP and clearly documenting our discussio
Maybe not in the first version but eventually nothing in the design
blocks us for supporting this. The SecretStore would need to be
available in the FunctionDefinitionFactory for this.
Cheers,
Timo
On 29.07.25 15:08, Ryan van Huuksloot wrote:
Overall the FLIP looks good to me.
Would the prop
Hi Dawid,
thanks for proposing this FLIP. Overall it fits into existing concepts
and completes the syntax.
+1 for this
Cheers,
Timo
On 28.07.25 15:31, Dawid Wysakowicz wrote:
Hi,
I'd like to start a discussion of FLIP-539: Support WITH Clause in CREATE
FUNCTION Statement in Flink SQL [1].
looks well, +1 from my side.
Could you draft(update) current FLIP docs thus we can have some
specific
discussions later?
Best,
Leonard
2025 6月 26 15:06，Timo Walther 写道：
Hi everyone,
sorry for the late reply, feature freeze kept me busy. Mayank, Hao
and
I
synced offline and came up we
Timo Walther created FLINK-38103:
Summary: DataTypeFactory cannot restore inline structured types
Key: FLINK-38103
URL: https://issues.apache.org/jira/browse/FLINK-38103
Project: Flink
Issue
Timo Walther created FLINK-38090:
Summary: TableResult.collect() returns incorrect SQL inline
structured types
Key: FLINK-38090
URL: https://issues.apache.org/jira/browse/FLINK-38090
Project: Flink
25 04:01, Leonard Xu wrote:
Thanks Timo for joining this thread.
I agree that this feature is needed by the community; the current disagreement
is only about the implementation method or solution.
Your thoughts looks generally good to me, looking forward to your proposal.
Best,
Leonard
2025 6月 6 22
s feedback
quickly.
Kind regards,
Gustavo de Morais
On Thu, 19 Jun 2025 at 15:51, Timo Walther
wrote:
Hi everyone,
I'm currently polishing FLIP-440, I would like to apply some last
minute
changes before the first release of PTFs for Flink 2.1. I've
already
collected initial
Hi everyone,
I'm currently polishing FLIP-440, I would like to apply some last minute
changes before the first release of PTFs for Flink 2.1. I've already
collected initial user feedback and it seems that the name for
annotations of table arguments is not precise enough.
As always, naming is
Timo Walther created FLINK-37974:
Summary: Avoid confusion when declaring table arguments
Key: FLINK-37974
URL: https://issues.apache.org/jira/browse/FLINK-37974
Project: Flink
Issue Type
Timo Walther created FLINK-37956:
Summary: Update SQL gateway for inline structured types
Key: FLINK-37956
URL: https://issues.apache.org/jira/browse/FLINK-37956
Project: Flink
Issue Type
Hi everyone,
thanks for this healthy discussion. Looking at high number of
participants, it looks like we definitely want this feature. We just
need to figure out the "how".
This reminds me very much of the discussion we had for CREATE FUNCTION.
There, we discussed whether functions should b
+1 (binding)
We should still check whether changes to QueryOperationVisitor are
necessary but this is internal API and should not the FLIP. The public
API looks correct to me.
Cheers,
Timo
On 12.05.25 18:50, Hao Li wrote:
Hi everyone,
I'd like to start a vote on FLIP-526: Model ML_PREDICT
Timo Walther created FLINK-37862:
Summary: Implement data type improvements for StructuredType
Key: FLINK-37862
URL: https://issues.apache.org/jira/browse/FLINK-37862
Project: Flink
Issue
Timo Walther created FLINK-37861:
Summary: FLIP-520: Simplify StructuredType handling
Key: FLINK-37861
URL: https://issues.apache.org/jira/browse/FLINK-37861
Project: Flink
Issue Type: New
d the hint based options? And why?
BTW, I feel that we can do better in dealing with similar FLIPs from
different contributors as well as FLIPs dormant for long. I'll start a
separate discussion on that rather than derail this thread.
Thanks,
Jiangjie (Becket) Qin
On Mon, May 26, 2025 at
-1
This FLIP has been subsumed by FLIP-498: AsyncTableFunction for async
table function support [1]. In the discussion for FLIP-498, we decided
to discard FLIP-313 as it has been abandoned for a while.
I hope this is ok for everyone. @Alan might give some timeline when this
feature will land
e end, most stuff should be reusable from the PTF work.
Cheers,
Timo
On 12.05.25 16:46, Timo Walther wrote:
+1 to continue to voting.
Thanks,
Timo
On 11.05.25 18:47, Hao Li wrote:
Hi all,
If there are no more discussions. I will start voting tomorrow.
Thanks,
Hao
On Thu, May 8, 2025 at 10:
+1 to continue to voting.
Thanks,
Timo
On 11.05.25 18:47, Hao Li wrote:
Hi all,
If there are no more discussions. I will start voting tomorrow.
Thanks,
Hao
On Thu, May 8, 2025 at 10:38 AM Hao Li wrote:
Hi Ron,
whether the predict or evaluate introduced in this FLIP can be
serialized to
+1 (binding)
Regards,
Timo
On 12.05.25 07:58, Ron Liu wrote:
+1 (binding)
Best,
Ron
Hao Li 于2025年5月10日周六 02:35写道：
+1 (non-binding)
Thanks,
Hao
On Fri, May 9, 2025 at 3:41 AM Arvid Heise wrote:
+1 (binding)
Cheers
On Wed, May 7, 2025 at 6:37 PM Gustavo de Morais
Hi everyone,
I'd l
Hi Hao,
please note that 72 hours in VOTE threads refers to business days so
excluding weekends. This vote should be open for at least 1 more day.
Regards,
Timo
On 11.05.25 18:19, Hao Li wrote:
Hi Dev,
I'm happy to announce that FLIP-525: Model ML_PREDICT, ML_EVALUATE
Implementation Desig
Hi everyone,
I'm happy to announce that FLIP-520: Simplify StructuredType handling
[1] has been accepted.
There were 6 approving votes, 3 of which were binding:
- Sergey Nuyanzin (binding)
- Ferenc Csaky (binding)
- Ron Liu (binding)
- Hao Li (non-binding)
- Gustavo de Morais (non-binding)
-
Thanks everyone. We have enough votes. I will close the vote now and
announce the result in a separate email.
Cheers,
Timo
On 06.05.25 14:49, Ramin Gharib wrote:
+1 (non-binding)
Thanks for driving this!
Best,
Ramin
On Tue, May 6, 2025 at 12:04 PM Timo Walther wrote:
Hi everyone,
I&#
+1 (binding)
Thanks for working on this!
Best,
Timo
On 07.05.25 11:08, Xuannan Su wrote:
Hi everyone,
I'd like to start a vote on FLIP-521: Integrating Variant Type into
Flink: Enabling Efficient Semi-Structured Data Processing[1], which
has been discussed in this thread[2].
The vote will be
Timo Walther created FLINK-37763:
Summary: Support multiple tables with set semantics
Key: FLINK-37763
URL: https://issues.apache.org/jira/browse/FLINK-37763
Project: Flink
Issue Type: Sub
Hi everyone,
I'd like to start a vote on FLIP-520: Simplify StructuredType handling
[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]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-520%
Hi everyone,
if there are no objections, I would start a voting thread by tomorrow.
Thanks,
Timo
On 29.04.25 11:46, Timo Walther wrote:
Hi Hao,
thanks for your feedback. Currently, the Python API does not support
structured types at all. So this might require another FLIP in the
future
Hi Xuannan,
thank you for updating the FLIP and addressing my comments. The FLIP is
in a very good shape now, +1 for voting. I just found some last
remaining items that would be good to be addressed in the FLIP. But not
blocker for the voting process:
> isScalar()
I thought about the naming
Hi Ramin,
it was a mistake to support the EXPLAIN STATEMENT SET syntax in the
first place. We support `EXPLAIN SELECT` and `EXPLAIN CREATE TABLE`, so
EXPLAIN + verb, we should have done the same for `EXECUTE`.
+1 for the proposal.
Cheers,
Timo
On 30.04.25 11:55, Gustavo de Morais wrote:
I
cy between STRUCT and ROW but tbh
I have more issues with ROW than with STRUCT. (What is even the meaning of
a nested ROW?)
So +1 with your proposal and maybe we can deprecate ROW at some later point
in time.
Best,
Arvid
On Thu, Apr 24, 2025 at 11:57 AM Timo Walther wrote:
Hi Arvid, Hi Hao,
Timo Walther created FLINK-37745:
Summary: ChangelogModeJsonSerializer doesn't handle partial deletes
Key: FLINK-37745
URL: https://issues.apache.org/jira/browse/FLINK-37745
Project:
forward to the detailed design of the subsequent shredding
optimizations.
Best,
Lincoln Lee
Timo Walther 于2025年4月22日周二 16:51写道：
+1 for this feature. Having a VARIANT type makes a lot of sense and
together with an OBJECT type will make semi-structured data processing
in Flink easier.
Currently,
hat wants to collect results (in your last example
what is t.execute().collect(); returning? How does that work in the
multi-user setup sketched above? Wouldn't it be easier that the consumer
explicitly gives us the POJO type that it expects?)
* Any DataStream conversion
* Any UDF
However, at t
lse with different fields and then in
Table api, it's not compatible.
Hao
On Tue, Apr 22, 2025 at 9:39 AM Timo Walther wrote:
Hi Arvid, Hi Sergey,
thanks for your feedback. I updated the FLIP accordingly but let me
answer your questions
here as well:
> Are we going to enforce that th
n
do I understand it correct that after this FLIP we can execute of
`typeof` against result of `OBJECT_OF`
for instance
SELECT typeof(OBJECT_OF(
'com.example.User',
'name', 'Bob',
'age', 42
));
should return `STRUCTURED<'com.example.User',
rais
wrote:
Thanks for the small but important changes proposed. IMO, these are
essential for dealing with these directly in SQL.
On 2025/04/10 05:54:58 Timo Walther wrote:
Hi everyone,
I would like to start a discussion about FLIP-520: Simplify
StructuredType handling [1].
Flink SQL alread
Hi everyone,
I would like to ask again for feedback on this FLIP. It is a rather
small change but with big impact on usability for structured data.
Are there any objections? Otherwise I would like to continue with voting
soon.
Thanks,
Timo
On 10.04.25 07:54, Timo Walther wrote:
Hi
+1 for this feature. Having a VARIANT type makes a lot of sense and
together with an OBJECT type will make semi-structured data processing
in Flink easier.
Currently, I'm catching up with notifications after the easter holidays,
but happy to give some feedback by tomorrow or Thursday as well.
flink-table/flink-table-planner/src/main/scala/org/apache/flink/table/planner/plan/nodes/physical/stream/StreamPhysicalLookupJoin.scala#L41
[3]
https://github.com/apache/flink/blob/master/flink-table/flink-table-common/src/main/java/org/apache/flink/table/connector/source/LookupTableSource.java#L
Timo Walther created FLINK-37671:
Summary: ChangelogMode.toString returns invalid string for partial
deletes
Key: FLINK-37671
URL: https://issues.apache.org/jira/browse/FLINK-37671
Project: Flink
Timo Walther created FLINK-37651:
Summary: Simplify StaticArgument builders for easier type inference
Key: FLINK-37651
URL: https://issues.apache.org/jira/browse/FLINK-37651
Project: Flink
Hi everyone,
I would like to start a discussion about FLIP-520: Simplify
StructuredType handling [1].
Flink SQL already supports structured types in the engine, serializers,
UDFs, and connector interfaces. However, currently only Table API was
able to make use of them. While UDFs can take ob
Timo Walther created FLINK-37632:
Summary: Add ChangelogFunction interface
Key: FLINK-37632
URL: https://issues.apache.org/jira/browse/FLINK-37632
Project: Flink
Issue Type: Sub-task
Hi Gabor,
great that you already try out PTFs. I'm in the process of writing
documentation for it. Including a list of limitations.
Please note that PTF won't be support in batch mode in the first phase.
For stateful PTFs we would need to use a batch state backend and also
other code paths a
Timo Walther created FLINK-37599:
Summary: Consider on_time argument for column expansion
Key: FLINK-37599
URL: https://issues.apache.org/jira/browse/FLINK-37599
Project: Flink
Issue Type
Timo Walther created FLINK-37598:
Summary: Support ListView and MapView in PTFs
Key: FLINK-37598
URL: https://issues.apache.org/jira/browse/FLINK-37598
Project: Flink
Issue Type: Sub-task
operations on it as well.
Cheers,
Gyula
On Fri, Mar 28, 2025 at 7:39 AM Timo Walther wrote:
Hi Gabor,
great that you already try out PTFs. I'm in the process of writing
documentation for it. Including a list of limitations.
Please note that PTF won't be support in batch mode in th
Timo Walther created FLINK-37547:
Summary: Add initial document for PTFs
Key: FLINK-37547
URL: https://issues.apache.org/jira/browse/FLINK-37547
Project: Flink
Issue Type: Sub-task
Hi everyone,
I would like to start a discussion about FLIP-517: Better Handling of
Dynamic Table Primitives with PTFs [1].
In the past months, I have spent a significant amount of time with SQL
semantics and the SQL standard around PTFs, when designing and
implementing FLIP-440 [2]. For thos
,
Yash Anand
On Tue, Mar 11, 2025 at 5:55 AM Timo Walther wrote:
Hi Yash,
thanks for updating the FLIP.
Here is more feedback from my side:
Add `option(ConfigOption configOption, T value)` similar to
`TableDescriptor`.
Use `comment()` instead of `setComment` to be in sync with
`TableDescriptor
Hi Yash,
could you provide the full API of the ModelDescriptor in the FLIP?
Thanks,
Timo
On 10.03.25 16:55, Mingge Deng wrote:
Thanks Yash!
+1 (binding)
Best,
Mingge
On Mon, Mar 10, 2025 at 8:51 AM Dawid Wysakowicz
wrote:
+1 (binding)
Best,
Dawid
On Wed, 19 Feb 2025 at 18:37, Hao Li
Timo Walther created FLINK-37466:
Summary: A helper function for DEFAULT in Table API
Key: FLINK-37466
URL: https://issues.apache.org/jira/browse/FLINK-37466
Project: Flink
Issue Type: Sub
Timo Walther created FLINK-37446:
Summary: Support asArgument in Table API
Key: FLINK-37446
URL: https://issues.apache.org/jira/browse/FLINK-37446
Project: Flink
Issue Type: Sub-task
Hi Dawid,
thanks for this proposal. This is a very nice improvement to the SQL
engine. Changelog normalize is a very state-intensive operation. Any
possibility to avoid it should be implemented.
Updating ChangelogMode is an elegant solution and avoid updating the
RowKind. When we introduced
+1 (binding)
Thanks for working on this!
Timo
On 11.03.25 11:05, Dawid Wysakowicz wrote:
Hi everyone,
I'd like to start a vote on FLIP-510: Drop ChangelogNormalize for
operations which don't need it[1]
which has been discussed in this thread [2].
The vote will be open for at least 72 hours u
est,
Leonard
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=334760466
2025年3月11日 01:19，Yash Anand 写道：
Hi Timo,
Thanks for pointing that out. I have added the full API of
the ModelDescriptor in the FLIP.
Thanks,
Yash Anand
On Mon, Mar 10, 2025 at 11:27 AM Timo Walther
wr
Timo Walther created FLINK-37457:
Summary: Support asArgument in Python Table API
Key: FLINK-37457
URL: https://issues.apache.org/jira/browse/FLINK-37457
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-37423:
Summary: Add support for PTFs in Table API
Key: FLINK-37423
URL: https://issues.apache.org/jira/browse/FLINK-37423
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-37402:
Summary: SQL testing sources produce incorrect watermarks
Key: FLINK-37402
URL: https://issues.apache.org/jira/browse/FLINK-37402
Project: Flink
Issue Type
Hi Gyula,
thanks for bringing this up. I agree that we should use one of the most
recent Kryo versions for Flink 2.0. Otherwise the community will suffer
again from incompatibilities and needs to wait for another major Flink
version. Thanks for starting this discussion. We should do it for 2.0
+1 (binding)
Thanks for working on this FLIP.
Best regards,
Timo
On 14.02.25 22:32, Alan Sheinberg wrote:
Hi everyone,
I'd like to start a vote on FLIP-491 [1]. It proposes
adding BundledAggregateFunction as an interface that aggregate function
UDFs can implement. The interface exposes a batc
Hi Mika,
thanks for bringing this up! I was actually quite surprised that we
don't use any kind of marking in our interfaces in the Python API yet.
Your proposal makes total sense. We should reuse the same annotation
categories that we use and agreed on in Java. Since the Python Table API
is
+1 (binding)
I went through the commit and checked for suspicious changes. Could not
found any.
Thanks,
Timo
On 18.02.25 18:52, Sergey Nuyanzin wrote:
Hi everyone,
Please review and vote on the release candidate #1 for the version
20.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not
you clarify what the table.exec.agg-bundled.size parameter
refers
to?
* Number of keys? Total number of rows? Number of rows per key?
* It would be nice to add the keys in the example
* How do the bundled agg functions interact with checkpointing?
* Are bundles sent out when a checkpoint
+1 (binding)
Thanks,
Timo
On 13.02.25 11:51, Sergey Nuyanzin wrote:
Hi everyone,
I'd like to start a vote on FLIP-508: Add support for Smile format for
Compiled plans [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
Timo Walther created FLINK-37302:
Summary: Support timers in PTFs
Key: FLINK-37302
URL: https://issues.apache.org/jira/browse/FLINK-37302
Project: Flink
Issue Type: Sub-task
Hi Gyula,
Sergey and I spent a significant amount of time in researching different
formats.
When we introduced CompiledPlan, the question whether we want to use a
binary format for performance and efficiency reasons immediately came
up, but we decided to postpone this discussion.
Back then
Timo Walther created FLINK-37269:
Summary: Add new DESCRIPTOR data type
Key: FLINK-37269
URL: https://issues.apache.org/jira/browse/FLINK-37269
Project: Flink
Issue Type: Sub-task
+1 (binding)
Thanks,
Timo
On 28.01.25 11:56, Fabian Hüske wrote:
+1 (binding) for this FLIP.
Thank you,
Fabian
On Tue, Jan 28, 2025 at 2:36 AM Natea Eshetu Beshada
wrote:
+1 (non-binding)
On Mon, Jan 27, 2025 at 3:02 PM Alan Sheinberg
wrote:
Hi everyone,
I'd like to start a vote on F
Timo Walther created FLINK-37219:
Summary: Support value state in PTFs
Key: FLINK-37219
URL: https://issues.apache.org/jira/browse/FLINK-37219
Project: Flink
Issue Type: Sub-task
+1 (binding)
Thanks for completing this effort.
Cheers,
Timo
On 23.01.25 22:39, Sergey Nuyanzin wrote:
+1 (binding)
Thanks for driving this.
On Thu, Jan 23, 2025, 11:57 Dawid Wysakowicz
wrote:
Hi, all.
I'd like to start a vote on FLIP-502: QueryOperation SQL Serialization
customization [1
Timo Walther created FLINK-37211:
Summary: Fix field resolution for PARTITION BY/ORDER BY
Key: FLINK-37211
URL: https://issues.apache.org/jira/browse/FLINK-37211
Project: Flink
Issue Type
Timo Walther created FLINK-37180:
Summary: Implement StreamOperator for PTF
Key: FLINK-37180
URL: https://issues.apache.org/jira/browse/FLINK-37180
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-37167:
Summary: Fix operand reordering in SqlValidatorImpl for
tableCharacteristics
Key: FLINK-37167
URL: https://issues.apache.org/jira/browse/FLINK-37167
Project: Flink
Thanks for the update Dawid.
From my point of view, the FLIP is ready for voting. Unless somebody
else has any objections?
Cheers,
Timo
On 15.01.25 10:20, Dawid Wysakowicz wrote:
Sure, I updated the FLIP
On Mon, 13 Jan 2025 at 15:20, Timo Walther wrote:
Hi Dawid,
thanks for proposing
Hi Alan,
thanks for giving us some context. It looks like FLIP-313 has not seen
any progress for 2 years. We can still revive FLIP-313 for the hint
discussion but start with config options. It makes sense that there is
consistency between AsycScalarFunction and AsyncTableFunction with
respect
Hi Alan,
thanks for proposing this FLIP. I agree that AsyncTableFunction is very
similar to AsyncScalarFunction and luckily, the Python component has
laid the foundation for this proposal.
Nothing to add from my side.
+1 for voting.
Regards,
Timo
On 02.01.25 20:47, Alan Sheinberg wrote:
I
Hi Alan,
thanks for sharing this FLIP with us. Sorry for the late reply. I think
the FLIP is already in a very good shape.
I like the approach that the BundledAggregateFunction is rather a
separate interface that can be implemented by advanced users. This
matches with the existing Specialize
Hi Dawid,
thanks for proposing this FLIP. It nicely completes the serialization
effort started with FLIP-393. I know naming is difficult, but could we
shorten and simplify the signatures further?
My suggestion would be:
OperationSerializationContext -> SqlSerializationContext
ExpressionSerial
Timo Walther created FLINK-37076:
Summary: Support PTF skeleton in planner
Key: FLINK-37076
URL: https://issues.apache.org/jira/browse/FLINK-37076
Project: Flink
Issue Type: Sub-task
Hi Huang,
I agree with Fabian that we should be careful with adding features to
DataStream API V2. Providing it as an extension rather than a base API
is definitely a good direction. Prepared built-in functions and
algorithms should rather go into a lib module.
Nevertheless, the DataStream A
Hi Sergey,
thanks for working on this. The FLIP is a nice continuation of started
efforts. The example of createTable doesn't use the flag. Otherwise +1
to vote, as it is not very controversial.
Cheers,
Timo
On 18.12.24 09:35, Sergey Nuyanzin wrote:
Hi Ron,
good catch,
I fixed it
thanks
O
Timo Walther created FLINK-36937:
Summary: Integrate PTF TypeInference into Table API
Key: FLINK-36937
URL: https://issues.apache.org/jira/browse/FLINK-36937
Project: Flink
Issue Type: Sub
+1 (binding)
Thanks,
Timo
On 13.12.24 01:37, Jim Hughes wrote:
Hi Sergey,
+1 (non-binding)
Cheers,
Jim
On Thu, Dec 12, 2024 at 2:51 PM Sergey Nuyanzin wrote:
Hi everyone,
I'd like to start a vote on FLIP-489: Add missing dropTable/dropView
methods
to TableEnvironment [1] which has been
+1
This FLIP is straightforward. No discussion necessary.
Thanks,
Timo
On 12.12.24 09:49, Sergey Nuyanzin wrote:
Thanks for the feedback Jim
Since there is no more feedback I will start voting soon
On Tue, Dec 10, 2024 at 12:23 AM Sergey Nuyanzin
wrote:
While reading it was surprised that
Timo Walther created FLINK-36789:
Summary: Update FunctionHint and ArgumentHint with StaticArguments
Key: FLINK-36789
URL: https://issues.apache.org/jira/browse/FLINK-36789
Project: Flink
nding)
- Shengkai Fang (binding)
- Fabian Hüske (binding)
- Dawid Wysakowicz (binding)
- Stefan Richter (binding)
- David Radley (non-binding)
- Martijn Visser (binding)
- Timo Walther (binding)
There are no disapproving votes.
Thanks everyone!
Best,
Timo
[1]
https://cwiki.apache.org/confluence/
the vote supposed to happen in a new thread?
Cheers,
Jim
On Mon, Nov 11, 2024 at 9:46 AM Konstantin Knauf
wrote:
+1 (binding)
Am Mo., 11. Nov. 2024 um 15:20 Uhr schrieb Sergey Nuyanzin <
snuyan...@apache.org>:
Thanks for this great improvement
+1 (binding)
On 2024/11/11 13:42:
Timo Walther created FLINK-36707:
Summary: Integrate PTF TypeInference into Calcite validator
Key: FLINK-36707
URL: https://issues.apache.org/jira/browse/FLINK-36707
Project: Flink
Issue
Timo Walther created FLINK-36706:
Summary: Update TypeInferenceExtractor for PTFs
Key: FLINK-36706
URL: https://issues.apache.org/jira/browse/FLINK-36706
Project: Flink
Issue Type: Sub-task
Timo Walther created FLINK-36704:
Summary: Update TypeInference with StaticArgument and
StateTypeStrategy
Key: FLINK-36704
URL: https://issues.apache.org/jira/browse/FLINK-36704
Project: Flink
Timo Walther created FLINK-36705:
Summary: Add ProcessTableFunction class and annotations
Key: FLINK-36705
URL: https://issues.apache.org/jira/browse/FLINK-36705
Project: Flink
Issue Type
Timo Walther created FLINK-36703:
Summary: FLIP-440: User-defined SQL operators /
ProcessTableFunction (PTF)
Key: FLINK-36703
URL: https://issues.apache.org/jira/browse/FLINK-36703
Project: Flink
Hi everyone,
I'd like to start a vote on FLIP-440: User-defined SQL operators /
ProcessTableFunction (PTF) [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]
https://cwiki.apache.org/confluence/
Nov 8, 2024 at 6:03 PM Timo Walther wrote:
Hi David,
happy to answer your questions as well:
> 1. I wonder what class of scenarios that PTF’s do not do well in and
> that DataStream API would be preferable/required? Assuming we have PTF
> Map and List support.
DataStream API supp
taStream API windows, the rowtime of a watermark fired
operator is always T = W - 1. Because it needs to be smaller than the
current watermark.
> 2., 3. ,4.
I reworked/removed the affected sections.
Cheers,
Timo
On 08.11.24 17:47, Timo Walther wrote:
Hi Fabian,
thanks for this massiv
query which might not be
uncommon (UNION ALL multiple PTF branches). Sure, users could just set the
uid but do we want to fail a query for that?
Finally, I found a few minor mistakes that you might want to fix:
1. "Public Interfaces", "ProcessTableFunction", "The collec
1 - 100 of 1133 matches
Mail list logo
