Hi all,
A couple of first comments on this:
1. I'm missing the problem statement in the overall introduction. It
immediately goes into proposal mode, I would like to first read what is the
actual problem, before diving into solutions.
2. "Each ETL job creates snapshots with checkpoint info on
+1 (binding)
Thanks Shengkai for driving this FLIP.
Best,
Jingsong
On Thu, Dec 1, 2022 at 12:20 PM Shengkai Fang wrote:
>
> Hi All,
>
> Thanks for all the feedback so far. Based on the discussion[1] we seem
> to have a consensus, so I would like to start a vote on FLIP-273.
>
> The vote will
xiaogang zhou created FLINK-30256:
-
Summary: LogalWindowAgg can set the chaining Strategy to always
Key: FLINK-30256
URL: https://issues.apache.org/jira/browse/FLINK-30256
Project: Flink
Hi All,
Thanks for all the feedback so far. Based on the discussion[1] we seem
to have a consensus, so I would like to start a vote on FLIP-273.
The vote will last for at least 72 hours (Dec 5th at 13:00 GMT,
excluding weekend days) unless there is an objection or insufficient votes.
Best,
Hi devs:
I'd like to start a discussion about FLIP-276: Data Consistency of
Streaming and Batch ETL in Flink and Table Store[1]. In the whole data
stream processing, there are consistency problems such as how to manage the
dependencies of multiple jobs and tables, how to define and handle E2E
Shammon created FLINK-30255:
---
Summary: Throw exception for upper case fields is used in hive
metastore
Key: FLINK-30255
URL: https://issues.apache.org/jira/browse/FLINK-30255
Project: Flink
Issue
Hi Gyula,
This is a good model. I will prepare a PR. Jim and I will help the verification
and release process.
--
Best,
Ted Chang | Software Engineer | htch...@us.ibm.com
Hi All!
I think for this first version let's go with the following simple model:
1. We include the OLM bundle generation script in the operator git repo
before the release
2. We add one extra release verification step to the wiki with detailed
instructions on generating and verifying the bundle
Hi Yu,
Thanks for moving my comments to this thread! Also, thank you for
answering my questions; it is helping me understand the SQL Gateway
better.
5.
> Our idea is to introduce a new session option (like
'sql-client.result.fetch-interval') to control
the fetching requests sending frequency.
Martijn Visser created FLINK-30254:
--
Summary: Sync Pulsar updates to external Pulsar connector
repository
Key: FLINK-30254
URL: https://issues.apache.org/jira/browse/FLINK-30254
Project: Flink
Hi, Jim,
Thanks for your feedback, your suggestions are very good. I have replied in the
discussion
mail, please take a look.
> 2022年11月29日 03:18，Jim Hughes 写道：
>
> Hi Shengkai, Yu,
>
> Thanks for the FLIP! I have had a chance to read it, and it looks good. I
> do have some questions:
>
>
The vote has been closed. Thank you for your votes. Here is the result:
Binding votes (9 in total):
- Gyula Fóra
- Őrhidi Mátyás
- Yang Wang
- Rui Fan
- Dong Lin
- Thomas Weise
- Marton Balassi
- Yun Tang
- Maximilian Michels
Non-binding votes (6 in total):
- Rui Fan
- Zheng Yu Chen
-
Hi, all
Thanks Jim’s questions below. Here I’d like to reply to them.
> 1. For the Client Parser, is it going to work with the extended syntax
> from the Flink Table Store?
>
> 2. Relatedly, what will happen if an older Client tries to handle syntax
> that a newer service supports?
+1 (binding)
I hereby close the vote. I'll send the result in a separate email with the
subject "[RESULT][VOTE] FLIP-271: Autoscaling"
Thanks,
Max
On Wed, Nov 30, 2022 at 2:24 PM Yun Tang wrote:
> + 1 (binding)
>
> Best
> Yun Tang
>
> From: Mason Chen
> Sent:
Thanks Fabian.
Do you know if the legacy StreamingFileSink has the same issues? Not asking
you to do research but just wondering if you happen to know.
On Tue, Nov 29, 2022 at 8:46 AM Fabian Paul wrote:
> Hi folks,
>
> I did some initial investigation, and the problem seems twofold.
>
> If no
Hi, all,
Thank you very much for this interesting discussion.
TBH, Dong's proposal made me very excited. Our users don't need to be
tortured by choosing the right one among many strategies.
However, as Gen said, it may need to make some changes to the
RestartBackoffTimeStrategy interface as it
+ 1 (binding)
Best
Yun Tang
From: Mason Chen
Sent: Wednesday, November 30, 2022 12:52
To: dev@flink.apache.org
Subject: Re: [VOTE] FLIP-271: Autoscaling
+1 (non-binding)
On Tue, Nov 29, 2022 at 11:55 AM Ferenc Csaky
wrote:
> +1 (non-binding)
>
>
>
>
>
Yun Tang created FLINK-30253:
Summary: Introduce io executor for standalone checkpoint store
Key: FLINK-30253
URL: https://issues.apache.org/jira/browse/FLINK-30253
Project: Flink
Issue Type:
Hi,
Considering there has been no response for a long time, I want to start the
vote on Thursday.
Best,
Shengkai
Jingsong Li 于2022年11月24日周四 15:20写道：
> Thanks for the update!
>
> Looks good to me.
>
> Best,
> Jingsong
>
> On Thu, Nov 24, 2022 at 3:07 PM Shengkai Fang wrote:
> >
> > Hi,
Chesnay Schepler created FLINK-30252:
Summary: Publish flink-shaded pom
Key: FLINK-30252
URL: https://issues.apache.org/jira/browse/FLINK-30252
Project: Flink
Issue Type: Technical Debt
Hi everyone,
Please review and vote on the release candidate #1 for the
flink-connector-jdbc version v3.0.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
Note: This is the first externalized version of the JDBC connector.
The
Hi Dawid, Piotr
Very thanks for the discussion!
As a whole I think we are already consistent with the callback option, and I
don't
think I opposed that we could modify the current internal implementation. But
from
my side it is still not clear what the actual interfaces are proposing. Let me
ming li created FLINK-30251:
---
Summary: Move the IO with DFS during abort checkpoint to an
asynchronous thread.
Key: FLINK-30251
URL: https://issues.apache.org/jira/browse/FLINK-30251
Project: Flink
Rui Fan created FLINK-30250:
---
Summary: The flame graph type is wrong
Key: FLINK-30250
URL: https://issues.apache.org/jira/browse/FLINK-30250
Project: Flink
Issue Type: Bug
Components:
Hi everyone,
Please review and vote on the release candidate #1 for the
flink-connector-pulsar version v3.0.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
Note: this is equivalent to the Pulsar connector that was released with
Zhipeng Zhang created FLINK-30249:
-
Summary: TableUtils.getRowTypeInfo() creating wrong TypeInformation
Key: FLINK-30249
URL: https://issues.apache.org/jira/browse/FLINK-30249
Project: Flink
Hi,
I have a couple of remarks.
First a general one. For me the important part in the design of this API is
how to expose this to Flink users in public interfaces. Namely
ProcessFunction and StreamOperator. InternalTimerService is an internal
class, so we can change it and break it as needed in
Jingsong Lee created FLINK-30248:
Summary: Spark writer supports insert overwrite
Key: FLINK-30248
URL: https://issues.apache.org/jira/browse/FLINK-30248
Project: Flink
Issue Type: New
+1 (binding)
- Validated hashes/signature
- Verified that no binaries exist in the source archive
- Build the source with Maven
- Verified NOTICE file
- Verified versions in pom files are correct
- Verified SinkIntoDynamoDb sample application writes to DynamoDB
Thanks,
Danny
On Tue, Nov 29,
WindowOperator is not implemented by users. I can see that for
InternalTimerService we'll need
interface PendingTimerProcessor {
void onTimer(InternalTimer timer) {
doHandleTimer(timer);
}
I don't see a problem with that.
As you said ProcessingTimeService is a user facing interface and
Jingsong Lee created FLINK-30247:
Summary: Introduce Time Travel reading for table store
Key: FLINK-30247
URL: https://issues.apache.org/jira/browse/FLINK-30247
Project: Flink
Issue Type:
31 matches
Mail list logo
