Fan Hong created FLINK-30730:
Summary: StringIndexer cannot handle null values correctly when
training
Key: FLINK-30730
URL: https://issues.apache.org/jira/browse/FLINK-30730
Project: Flink
Matthias Pohl created FLINK-30729:
-
Summary: AggregateITCase generates stacktraces of
IllegalStateExceptions in Maven output but doesn't fail
Key: FLINK-30729
URL:
chenhaiyang created FLINK-30728:
---
Summary: Translate "Window Join" page of "Querys" into Chinese
Key: FLINK-30728
URL: https://issues.apache.org/jira/browse/FLINK-30728
Project: Flink
Issue
Matthias Pohl created FLINK-30727:
-
Summary: JoinReorderITCase.testBushyTreeJoinReorder failed due to
IOException
Key: FLINK-30727
URL: https://issues.apache.org/jira/browse/FLINK-30727
Project:
Thanks Matthias for the detailed explanation.
For the HA backend data structure, you are right. Even the different
components are running in a same JVM,
they have completely different connection infos. But it is not urgent to
use a single ZNode to store multiple connection entries for now.
I
chenhaiyang created FLINK-30726:
---
Summary: Translate "Over Aggregation" page of "Querys" into
Chinese
Key: FLINK-30726
URL: https://issues.apache.org/jira/browse/FLINK-30726
Project: Flink
Biao Liu created FLINK-30725:
Summary: FLIP-281: Sink Supports Speculative Execution For Batch
Job
Key: FLINK-30725
URL: https://issues.apache.org/jira/browse/FLINK-30725
Project: Flink
Issue
Yun Tang created FLINK-30724:
Summary: Update doc of kafka per-partition watermark to FLIP-27
source
Key: FLINK-30724
URL: https://issues.apache.org/jira/browse/FLINK-30724
Project: Flink
Issue
Shammon created FLINK-30723:
---
Summary: Introduce filter pushdown for parquet format
Key: FLINK-30723
URL: https://issues.apache.org/jira/browse/FLINK-30723
Project: Flink
Issue Type: Improvement
chenhaiyang created FLINK-30722:
---
Summary: Translate "Group Aggregation" page of "Querys" into
Chinese
Key: FLINK-30722
URL: https://issues.apache.org/jira/browse/FLINK-30722
Project: Flink
> Additionally, the configurable variables (operator name/id) are
logically not attached to the coordinator, but operators, so to me it
just doesn't make sense to structure it like this.
Chesnay, maybe we should clarify the terminology. To me, pperators (like
FLIP-27 source) can have two parts
Jark,
We were planning to discard the proposal due to some valid concerns raised
in the thread. Also, this proposal itself didn't really save too much code
duplication (maybe 100 lines or so).
I also thought that the shuffle operator for DataStream can be useful for
other connectors too. The
Pedro Mázala created FLINK-30721:
Summary: The confluent schema registry is not compatible with
Apicurio shcema registry
Key: FLINK-30721
URL: https://issues.apache.org/jira/browse/FLINK-30721
Matthias Pohl created FLINK-30720:
-
Summary:
KafkaChangelogTableITCase.testKafkaDebeziumChangelogSource failed due to a
topic already exist when creating it
Key: FLINK-30720
URL:
Matthias Pohl created FLINK-30719:
-
Summary: flink-runtime-web failed due to a corrupted
Key: FLINK-30719
URL: https://issues.apache.org/jira/browse/FLINK-30719
Project: Flink
Issue Type:
Andriy Redko created FLINK-30718:
Summary: Cannot assign instance of
java.lang.invoke.SerializedLambda to field
org.apache.flink.connector.opensearch.sink.OpensearchSink.emitter
Key: FLINK-30718
URL:
Thanks for the write-up Yanfei. It sounds reasonable to me, too. Moving
this into a dedicated discussion thread with the wiki article as the base
for that discussion makes sense. There is already a performance benchmark
article which could be extended [1]. We're working on documentation about
+1 for the proposal
Best,
Lijie
Martijn Visser 于2023年1月17日周二 21:54写道：
> Hi Yun Tang,
>
> +1 for the proposal. Thanks for driving this.
>
> Best regards,
>
> Martijn
>
> Op ma 16 jan. 2023 om 12:29 schreef Yanfei Lei :
>
> > Hi Yun,
> >
> > Thanks for kicking off this discussion, +1 for the
Hi everyone,
I just published a new FLIP to introduce operator state compression (1).
This feature is pretty straightforward to implement, so a PR is already
under review (2) but it appeared during the review that to be able to
insure backward compatibility of the operator state snapshots, we
Jiang Xin and I created a FLIP at the same time, so we have a conflict
on the FLIP number. As he published his just before mine, I incremented
this FLIP number to 290.
So I'm closing this thread and starting a new one with the new FLIP
number. Sorry for the duplicated content.
Best
Etienne
Chesnay Schepler created FLINK-30717:
Summary: Migrate Travis CI to Github Actions
Key: FLINK-30717
URL: https://issues.apache.org/jira/browse/FLINK-30717
Project: Flink
Issue Type:
Hi everyone,
I just published a new FLIP to introduce operator state compression (1).
This feature is pretty straightforward to implement, so a PR is already
under review (2) but it appeared during the review that to be able to
insure backward compatibility of the operator state snapshots, we
Hi Yun Tang,
+1 for the proposal. Thanks for driving this.
Best regards,
Martijn
Op ma 16 jan. 2023 om 12:29 schreef Yanfei Lei :
> Hi Yun,
>
> Thanks for kicking off this discussion, +1 for the proposal.
> In the past, we occasionally encountered flink-benchmarks compilation
> failures
Hi Yanfei,
Thanks for the proposal! Like Yuan mentioned, let's start a new discussion
thread to get a clean discussion of your proposal, but it already sounds
good to me.
Best regards,
Martijn
Op di 17 jan. 2023 om 10:41 schreef Yuan Mei :
> Hey Yanfei,
>
> Thanks so much for the efforts
Hi all,
As establish a read-only contract seems to be consensual approach, talking to
Lijie we saw two ways for doing this..
Option 1: UnmodifiableExecutionConfig that extends ExecutionConfig (just like
the UnmodifiableConfiguration)
Pros:
- we have all the get methods
- don't need to change
Thanks Yang for getting back to me.
I checked the connection information that's stored in the HA backend once
more. My previous proposal is based on a wrong assumption: The address we
store is the RPC endpoint's address. That address should be unique per
component which means that we shouldn't
Jett Dai created FLINK-30716:
Summary: [Flink SQL] SQL function TO_TIMESTAMP(string1[,
string2])'s result incorrect where string2 is default: '-MM-dd HH:mm:ss'
Key: FLINK-30716
URL:
Jiang Xin created FLINK-30715:
-
Summary: FLIP-289: Support Online Inference
Key: FLINK-30715
URL: https://issues.apache.org/jira/browse/FLINK-30715
Project: Flink
Issue Type: Improvement
Hi devs and users,
I'd like to share some highlights from the release sync on 1/17/2023.
- CI & Performance: totally 5 blocker issues. Owners should have been
pinged.
- FLIP-272 [1] has finished and there will be a blog post before 1.17
release.
- PR about publishing SBOM [2] has been merged,
Hey Yanfei,
Thanks so much for the efforts driving the whole process. It's great to see
that the performance benchmarks are indeed useful to help find regressions.
1. Regarding the procedure of how to use and understand the notification
reported from the slack channel #flink-dev-benchmarks, the
chenhaiyang created FLINK-30714:
---
Summary: Translate "Window Aggregation" page of "Querys" into
Chinese
Key: FLINK-30714
URL: https://issues.apache.org/jira/browse/FLINK-30714
Project: Flink
Gabor Somogyi created FLINK-30713:
-
Summary: Add Hadoop related k8s decorators exclude possibility
Key: FLINK-30713
URL: https://issues.apache.org/jira/browse/FLINK-30713
Project: Flink
32 matches
Mail list logo
