I've stumbled in an issue regarding flink-connector-base.
Since the externalized connectors rely on binary compatibility between
Flink minor versions, connector-base should never be bundled by an
externalized connector since connector-base may rely on internal APIs
(which ti is allowed to use
Nico Kruber created FLINK-29867:
---
Summary: Update maven-enforcer-plugin to 3.1.0
Key: FLINK-29867
URL: https://issues.apache.org/jira/browse/FLINK-29867
Project: Flink
Issue Type: Improvement
luoyuxia created FLINK-29861:
Summary: Optimize logic of enumerateSplits in HiveSource
Key: FLINK-29861
URL: https://issues.apache.org/jira/browse/FLINK-29861
Project: Flink
Issue Type:
Hi,
A while ago the Flink community decided to create a Slack workspace [1]. I
wonder, is there a particular reason why we created our own Slack workspace
and do not use the official ASF Slack [2]? It looks like most ASF projects
use the official Slack. Using the official Slack makes
This RC is canceled.
On 02/11/2022 20:20, Danny Cranmer wrote:
Hey,
It is very exciting to see the first RC for an externalized connector!
Thanks for all the effort setting up the release scripts and processes
Chesnay.
Just to confirm before I start verifying this, will there be an RC2 to
Chesnay Schepler created FLINK-29862:
Summary: Upgrade to flink-shaded 16.0
Key: FLINK-29862
URL: https://issues.apache.org/jira/browse/FLINK-29862
Project: Flink
Issue Type: Improvement
Hi,
We did something like this for the 1.14 release [1].
We did that in an async survey-style way approaching key contributors
directly. I also think the output was quite nice and we got positive
feedback for what we published.
I think Robert mentioned they did something similar in the past, with
christofe lintermans created FLINK-29864:
Summary: AvroDeserializationSchema.forSpecific still generates
genericdata.record
Key: FLINK-29864
URL: https://issues.apache.org/jira/browse/FLINK-29864
Hi,
Sorry for the delay, but I've given more thoughts into this. First I share
the same thoughts as Maximilian, that this FLIP is incomplete. As I
understand it, you are trying to hack existing code to expose small bits of
internal functionalities as part of the public API without solving many of
Note that this _shouldn't_ be a problem since connector-base is part of
the distribution and should usually be loaded first than the version
bundled by the connector.
On 03/11/2022 11:28, Chesnay Schepler wrote:
* rely on binary compatibility between Flink /*patch */versions
On 03/11/2022
Nico Kruber created FLINK-29865:
---
Summary: Allow configuring the JDK in build-nightly-dist.yml
Key: FLINK-29865
URL: https://issues.apache.org/jira/browse/FLINK-29865
Project: Flink
Issue
Weihua Hu created FLINK-29870:
-
Summary: Split ResourceActions to ResourceAllocator and
ResourceAllocationNotifier
Key: FLINK-29870
URL: https://issues.apache.org/jira/browse/FLINK-29870
Project: Flink
Hi everyone,
Please review and vote on the release candidate #2 for the version
3.0.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
Thanks yanfei for driving this!
Looking forward to further discussion w.r.t. the workflow.
Best regards,
Jing
On Mon, Oct 31, 2022 at 6:04 PM Mason Chen wrote:
> +1, thanks for driving this!
>
> On a side note, can we also ensure that a performance summary report for
> Flink major version
Chesnay Schepler created FLINK-29866:
Summary: Split flink-dist
Key: FLINK-29866
URL: https://issues.apache.org/jira/browse/FLINK-29866
Project: Flink
Issue Type: New Feature
+1 If we wanted to expose the OperatorCoordinator API, we should provide an
adequate interface. The FLIP partially addresses this by trying to factor
out RPC code which other coordinators might make use of, but there is
additional design necessary to realize a public operator API.
Just to be
Weihua Hu created FLINK-29869:
-
Summary: make ResourceActions declarative
Key: FLINK-29869
URL: https://issues.apache.org/jira/browse/FLINK-29869
Project: Flink
Issue Type: Sub-task
Chesnay Schepler created FLINK-29863:
Summary: Properly handle NaN/Infinity in OpenAPI spec
Key: FLINK-29863
URL: https://issues.apache.org/jira/browse/FLINK-29863
Project: Flink
Issue
Nico Kruber created FLINK-29868:
---
Summary: Dependency convergence error for
org.osgi:org.osgi.core:jar
Key: FLINK-29868
URL: https://issues.apache.org/jira/browse/FLINK-29868
Project: Flink
* rely on binary compatibility between Flink /*patch */versions
On 03/11/2022 11:25, Chesnay Schepler wrote:
I've stumbled in an issue regarding flink-connector-base.
Since the externalized connectors rely on binary compatibility between
Flink minor versions, connector-base should never be
Hi Max,
>From my experience, most ASF projects actually don't use the official
Slack, but their own instance. That has happened with Airflow, Iceberg,
Hudi etc.
The big problem of using the ASF Slack instance is that users can join any
Slack channel, including ones outside of Flink. Not to
Ohhh, I was confused. I thought that the proposal is to make
`CoordinatorContextBase` part of the public API.
However, I'm also against extracting `CoordinatorContextBase` as an
`@Internal` class as well.
1. Connectors shouldn't reuse internal classes. Using `@Internal`
Gyula Fora created FLINK-29871:
--
Summary: Upgrade operator Flink version and examples to 1.16
Key: FLINK-29871
URL: https://issues.apache.org/jira/browse/FLINK-29871
Project: Flink
Issue Type:
Gyula Fora created FLINK-29872:
--
Summary: JobDetailsInfo Rest endpoint breaking change in 1.16
Key: FLINK-29872
URL: https://issues.apache.org/jira/browse/FLINK-29872
Project: Flink
Issue Type:
Ah thank you Yuxia!
Following up on the conversation... Trying to return an empty null array
ARRAY proved a challenge. Not impossible, but I think it would
require a further discussion as to if we want to expose values with the
data type NULL in the output - currently there are a lot of
Addition: I'm not sure if Linen actually provides the messages that are
older, but I can't test that since we've only recently integrated it.
On Thu, Nov 3, 2022 at 2:23 PM Martijn Visser
wrote:
> Hi Max,
>
> From my experience, most ASF projects actually don't use the official
> Slack, but
According to Robert linen is supposed to show the entire history.
On 03/11/2022 14:27, Martijn Visser wrote:
Addition: I'm not sure if Linen actually provides the messages that are
older, but I can't test that since we've only recently integrated it.
On Thu, Nov 3, 2022 at 2:23 PM Martijn
Good findings!
I thought the new scripts ensured a pristine source release, will look
into that tomorrow.
CI passed for the RC so I'd currently assume it's a local issue. But I
remember seeing that particular error message on CI once in a while.
The archunit stored.rules files should not
I updated the source release on dist.apache.org.
On 03/11/2022 22:03, Chesnay Schepler wrote:
Good findings!
I thought the new scripts ensured a pristine source release, will look
into that tomorrow.
CI passed for the RC so I'd currently assume it's a local issue. But I
remember seeing
Daeyeon Bae created FLINK-29873:
---
Summary: CannotPlanException raised after "CROSS JOIN UNNEST"
Key: FLINK-29873
URL: https://issues.apache.org/jira/browse/FLINK-29873
Project: Flink
Issue
FYI, release-3.3 branch has been cut and is ready for the release process
for StateFun 3.3.0:
https://github.com/apache/flink-statefun/tree/release-3.3
On Tue, Nov 1, 2022 at 10:21 AM Tzu-Li (Gordon) Tai
wrote:
> Btw, I'll assume that we're using this thread to gather consensus for
>
Hello Chesnay,
-1 (binding)
I do not approve the release due to the source release [1] containing
binaries, the full /target folder is present for each module. Assuming we
missed a "mvn clean"
Other concerns/questions:
- I performed a fresh clone of the source and checked out the tag. The
build
Caizhi Weng created FLINK-29876:
---
Summary: Explicitly throw exception from Table Store sink when
unaligned checkpoint is enabled
Key: FLINK-29876
URL: https://issues.apache.org/jira/browse/FLINK-29876
luoyuxia created FLINK-29878:
Summary: Fail to use flink-sql-connector-hive-3.1.3
Key: FLINK-29878
URL: https://issues.apache.org/jira/browse/FLINK-29878
Project: Flink
Issue Type: Bug
penney created FLINK-29877:
---
Summary: Failed to fetch next result
Key: FLINK-29877
URL: https://issues.apache.org/jira/browse/FLINK-29877
Project: Flink
Issue Type: Bug
Components:
It's TableA union all TableB union all TableC.The data volume of the three
tables is not large. They are all about hundreds. I used the hive connector to
read the three tables. The sqlmode is default.When it's running and report a
error:Failed to fetch next result.Then I suspected that it was a
Leonard Xu created FLINK-29874:
--
Summary: Streaming File Sink end-to-end test failed on azure
Key: FLINK-29874
URL: https://issues.apache.org/jira/browse/FLINK-29874
Project: Flink
Issue Type:
Shengkai Fang created FLINK-29875:
-
Summary: Can not find JobConf when using Hive Connector
Key: FLINK-29875
URL: https://issues.apache.org/jira/browse/FLINK-29875
Project: Flink
Issue
Leonard Xu created FLINK-29859:
--
Summary: TPC-DS end-to-end test with adaptive batch scheduler
failed due to oo non-empty .out files.
Key: FLINK-29859
URL: https://issues.apache.org/jira/browse/FLINK-29859
Noel O'Connor created FLINK-29860:
-
Summary: Pulsar connector bug when using Hybrid.Builder
Key: FLINK-29860
URL: https://issues.apache.org/jira/browse/FLINK-29860
Project: Flink
Issue Type:
40 matches
Mail list logo
