Targeted for 1.14.
On 6/22/2021 6:16 PM, Etienne Chauchot wrote:
Hi everyone,
I was thinking today about the migration from akka 2.5.21 that we
currently use to 2.6.x. I saw Chesnay has been thinking about this as
well as he just opened this ticket (1) :)
Besides the general good reasons
lqjacklee created FLINK-23103:
-
Summary: Provide Inteceptor for connector
Key: FLINK-23103
URL: https://issues.apache.org/jira/browse/FLINK-23103
Project: Flink
Issue Type: New Feature
+1 for appending this to community guidelines for merging PRs.
@Till Rohrmann
I agree that with this approach unstable tests will not block other
commit merges. However, it might be hard to prevent merging commits
that are related to those tests and should have been passed them. It's
true that
Xintong Song created FLINK-23105:
Summary:
YARNSessionCapacitySchedulerITCase.testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots
fails on azure
Key:
Seems there's no objections.
After reaching out to the release managers, the work will be divided as
follows.
- 1.11.4: Godfrey
- 1.12.5: Jingsong
- 1.13.2: Yun
I'll also be helping with the release managers where PMC authority is
required in the release process.
Thank you~
Xintong Song
On
+1 for dropping if there is no strong demand from the community.
I'm willing to help with the removal of e2e tests part.
Best,
Yangze Guo
On Wed, Jun 23, 2021 at 10:09 AM Xintong Song wrote:
>
> +1 for dropping.
>
> I like Seth's idea. I don't have any real Mesos experience either.
> According
Xintong Song created FLINK-23104:
Summary: flink-statebackend-changelog does not build with scala
2.12
Key: FLINK-23104
URL: https://issues.apache.org/jira/browse/FLINK-23104
Project: Flink
FYI, I updated the FLIP accordingly. To sum up, Flink will throw an
exception and tell user to configure an internal
"fine-grained.shuffle-mode.all-blocking" to be true in this scenario.
Best,
Yangze Guo
On Tue, Jun 22, 2021 at 2:20 PM Yangze Guo wrote:
>
> Thanks for the comment, Xintong.
>
>
+1 for dropping.
I like Seth's idea. I don't have any real Mesos experience either.
According to this article [1], it looks like we can deploy a standalone
cluster on Mesos similar to Kubernetes. However, we should only do it if
there's indeed a strong demand from the community for deploying a
Hi everyone,
I was hoping for more feedback from other committers, but seems like this
is not happening, so here's my proposal for immediate changes:
* Ignore tickets with a fixVersion for all rules but the stale-unassigned
role.
* We change the time intervals as follows, accepting reality a
Jingsong Lee created FLINK-23106:
Summary: RetractableTopNFunction should send retract first and
then send insert
Key: FLINK-23106
URL: https://issues.apache.org/jira/browse/FLINK-23106
Project:
Hi Piotr,
the bot does not close with "Won't fix", it closes with resolution
"Auto-Closed". It also says in a comment:
This issue was labeled "{warning_label}" {warning_days} days ago and has
not received any updates so I have gone ahead and closed it. If you are
still affected by this or would
Jingsong Lee created FLINK-23107:
Summary: Separate deduplicate rank from rank functions
Key: FLINK-23107
URL: https://issues.apache.org/jira/browse/FLINK-23107
Project: Flink
Issue Type:
退订
JING ZHANG created FLINK-23079:
--
Summary: HiveTableSinkITCase fails
Key: FLINK-23079
URL: https://issues.apache.org/jira/browse/FLINK-23079
Project: Flink
Issue Type: Bug
Components:
Thanks for the comment, Xintong.
I used to wonder if it was reasonable or worthwhile to introduce a
configuration like "table.exec.shuffle-mode" for DataStream API.
Narrow down the scope of effect sounds good to me.
Best,
Yangze Guo
On Tue, Jun 22, 2021 at 2:08 PM Xintong Song wrote:
>
> I
Piotr Nowojski created FLINK-23078:
--
Summary: Scheduler Benchmarks not compiling
Key: FLINK-23078
URL: https://issues.apache.org/jira/browse/FLINK-23078
Project: Flink
Issue Type: Bug
I second Zhu and Till's opinion.
Failing with an exception that also includes how to resolve the problem
sounds better, in terms of making it explicit to users that pipelined edges
are replaced with blocking edges.
Concerning absence of knobs tuning the edge types, we can introduce a
Dawid Wysakowicz created FLINK-23080:
Summary: Add finish method to the SinkFunction
Key: FLINK-23080
URL: https://issues.apache.org/jira/browse/FLINK-23080
Project: Flink
Issue Type:
Thanks for volunteering.
A quick update about FLINK-23011. It turned out to be only an issue in the
master, so we don't need to block bug fix releases on this issue.
Best,
Piotrek
wt., 22 cze 2021 o 05:20 Xintong Song napisał(a):
> Thanks Dawid for starting the discussion, and thanks Yun,
Last week I spent some time looking into making flink-runtime scala
free, which effectively means to move the Akka-reliant classes to
another module, and load that module along with Akka and all of it's
dependencies (including Scala) through a separate classloader.
This would finally decouple
Chesnay Schepler created FLINK-23081:
Summary: Move Executors#directExecutorContext to AkkaFutureUtils
Key: FLINK-23081
URL: https://issues.apache.org/jira/browse/FLINK-23081
Project: Flink
Hi Austin,
Thank you for your thoughts. This is where this discussion stops. This
email thread already contains more characters than the implementation and
what is needed for the next 20 years of maintenance.
It is great that you have a view on modern solutions and thank you for
offering your
Chesnay Schepler created FLINK-23082:
Summary: Split AkkaRpcServiceUtils
Key: FLINK-23082
URL: https://issues.apache.org/jira/browse/FLINK-23082
Project: Flink
Issue Type: Sub-task
Chesnay Schepler created FLINK-23083:
Summary: Isolate RpcConnectionTest from runtime implementations
Key: FLINK-23083
URL: https://issues.apache.org/jira/browse/FLINK-23083
Project: Flink
Chesnay Schepler created FLINK-23084:
Summary: Move ExecutorThreadFactory to flink-core
Key: FLINK-23084
URL: https://issues.apache.org/jira/browse/FLINK-23084
Project: Flink
Issue Type:
Shuo Cheng created FLINK-23086:
--
Summary: Add getRuntimeExecutionMode to StreamExecutionEnvironment
Key: FLINK-23086
URL: https://issues.apache.org/jira/browse/FLINK-23086
Project: Flink
Issue
Chesnay Schepler created FLINK-23087:
Summary: AddressResolution should be a top-level class
Key: FLINK-23087
URL: https://issues.apache.org/jira/browse/FLINK-23087
Project: Flink
Issue
Hi everyone,
In the past a couple of weeks, I've observed several times that PRs are
merged without a green light from the CI tests, where failure cases are
considered *unrelated*. This may not always cause problems, but would
increase the chance of breaking our code base. In fact, it has
Adding the InterruptException to the write method would make it explicit
that the write call can block but must react to interruptions (e.g. when
Flink wants to cancel the operation). I think this makes the contract a bit
clearer.
I think starting simple and then extending the API as we see the
Thanks for bringing this topic to our attention Xintong. I think your
proposal makes a lot of sense and we should follow it. It will give us
confidence that our changes are working and it might be a good incentive to
quickly fix build instabilities. Hence, +1.
Cheers,
Till
On Tue, Jun 22, 2021
Chesnay Schepler created FLINK-23090:
Summary: Add RpcSystem abstraction
Key: FLINK-23090
URL: https://issues.apache.org/jira/browse/FLINK-23090
Project: Flink
Issue Type: Sub-task
I'm adding Oleksandr from Criteo to this thread, they've mentioned in the
past that they are using Flink on Mesos (IIRC the only company that seemed
to be doing so)
I'm personally fine with dropping Mesos support.
On Tue, Jun 22, 2021 at 10:29 AM Chesnay Schepler
wrote:
> Last week I spent
I think this is overall a good idea. So +1 from my side.
However, I'd like to put a higher priority on infrastructure then, in
particular docker image/artifact caches.
On Tue, Jun 22, 2021 at 11:50 AM Till Rohrmann wrote:
> Thanks for bringing this topic to our attention Xintong. I think your
>
One way to address the problem of regularly failing tests that block
merging of PRs is to disable the respective tests for the time being. Of
course, the failing test then needs to be fixed. But at least that way we
would not block everyone from making progress.
Cheers,
Till
On Tue, Jun 22, 2021
Chesnay Schepler created FLINK-23088:
Summary: Add flink-rpc-core module
Key: FLINK-23088
URL: https://issues.apache.org/jira/browse/FLINK-23088
Project: Flink
Issue Type: Sub-task
Chesnay Schepler created FLINK-23091:
Summary: Bump Akka to 2.6
Key: FLINK-23091
URL: https://issues.apache.org/jira/browse/FLINK-23091
Project: Flink
Issue Type: Sub-task
Hey,
Agreed on starting with a blocking `write`. I've adapted the FLIP accordingly.
For now I've chosen to add the `InterruptedException` to the `write` method
signature as I'm not fully understanding the implications of swallowing the
exception. Depending on the details of the code that is
退订
| |
lizikunn
|
|
lizik...@163.com
|
签名由网易邮箱大师定制
Hi everyone,
I do like the idea of keeping the actual change outside of Flink but to
enable Flink to support such a use case (different authentication
mechanisms). I think this is a good compromise for the community that
combines long-term maintainability with support for new use-cases. I am
Chesnay Schepler created FLINK-23085:
Summary: Consolidate FutureUtils to flink-core
Key: FLINK-23085
URL: https://issues.apache.org/jira/browse/FLINK-23085
Project: Flink
Issue Type:
Chesnay Schepler created FLINK-23089:
Summary: Add flink-rpc-akka module
Key: FLINK-23089
URL: https://issues.apache.org/jira/browse/FLINK-23089
Project: Flink
Issue Type: Sub-task
Huang Xingbo created FLINK-23092:
Summary: Fix built-in functions are unsupported in Python Group
Window UDAF
Key: FLINK-23092
URL: https://issues.apache.org/jira/browse/FLINK-23092
Project: Flink
Hi everyone,
First, Marton and I had a brief conversation yesterday offline and
discussed exploring the approach of exposing the authentication
functionality via an API. So, I am looking forward to your proposal in that
direction. The benefit of such a solution would be that it is extensible
for
I'd be ok with dropping support for Mesos if it helps us to clear our
dependencies in the flink-runtime module. If we do it, then we should
probably update our documentation with a pointer to the latest Flink
version that supports Mesos in case of users strictly need Mesos.
Cheers,
Till
On Tue,
Thanks a lot, Yun, Godfrey, and Jingsong for being our release managers!
Creating these bug-fix releases will be super helpful for our users.
Cheers,
Till
On Tue, Jun 22, 2021 at 9:59 AM Piotr Nowojski wrote:
> Thanks for volunteering.
>
> A quick update about FLINK-23011. It turned out to be
+1 for dropping. Frankly speaking, I don't see it having any future (and D2iQ
agrees).
If there is a surprisingly huge demand, I'd try to evaluate plugins for it.
On Tue, Jun 22, 2021 at 11:46 AM Till Rohrmann wrote:
> I'd be ok with dropping support for Mesos if it helps us to clear our
>
It is a good principle to run all tests successfully with any change. This
means a lot for project's stability and development. I am big +1 for this
proposal.
Best
liujiangang
Till Rohrmann 于2021年6月22日周二 下午6:36写道：
> One way to address the problem of regularly failing tests that block
>
Hi there,
After the discussion in [1], I’d like to open a voting thread for FLIP-171 [2],
which proposes a base implementation for sinks that support async requests.
The vote will be open until June 25 (72h), unless there is an objection or not
enough votes.
Cheers, Steffen
[1]
godfrey he created FLINK-23094:
--
Summary: encounter thread-safe problem when using
StreamExecutionEnvironment#initializeContextEnvironment in multiple-threads
environment
Key: FLINK-23094
URL:
Stephan Ewen created FLINK-23093:
Summary: Limit number of I/O pool and Future threads in Mini
Cluster
Key: FLINK-23093
URL: https://issues.apache.org/jira/browse/FLINK-23093
Project: Flink
Dawid Wysakowicz created FLINK-23095:
Summary: Close the channel unspilling thread pool after restore
Key: FLINK-23095
URL: https://issues.apache.org/jira/browse/FLINK-23095
Project: Flink
shizhengchao created FLINK-23096:
Summary: HiveParser could not attach the sessionstate of hive
Key: FLINK-23096
URL: https://issues.apache.org/jira/browse/FLINK-23096
Project: Flink
Issue
David Anderson created FLINK-23100:
--
Summary: Update pyflink walkthrough playground for 1.13
Key: FLINK-23100
URL: https://issues.apache.org/jira/browse/FLINK-23100
Project: Flink
Issue
David Anderson created FLINK-23099:
--
Summary: Update table walkthrough playground for 1.13
Key: FLINK-23099
URL: https://issues.apache.org/jira/browse/FLINK-23099
Project: Flink
Issue Type:
Sorry if this is a naive question, I don't have any real Mesos experience.
Is it possible to deploy a standalone cluster on top of Mesos in the same
way you can with Kubernetes? If so, and there is still Mesos demand from
the community, we could document that process as the recommended deployment
Nico Kruber created FLINK-23101:
---
Summary: Flame Graphs initial view says it is 18800 days in the
past
Key: FLINK-23101
URL: https://issues.apache.org/jira/browse/FLINK-23101
Project: Flink
Nico Kruber created FLINK-23102:
---
Summary: Accessing FlameGraphs while not being enabled returns an
exception
Key: FLINK-23102
URL: https://issues.apache.org/jira/browse/FLINK-23102
Project: Flink
Dawid Wysakowicz created FLINK-23097:
Summary: 'Queryable state (rocksdb) with TM restart end-to-end
test' fails on azure
Key: FLINK-23097
URL: https://issues.apache.org/jira/browse/FLINK-23097
David Anderson created FLINK-23098:
--
Summary: Update operations playground for 1.13
Key: FLINK-23098
URL: https://issues.apache.org/jira/browse/FLINK-23098
Project: Flink
Issue Type:
I am in favor of dropping the support for Mesos.
In terms of the landscape for users leveraging Mesos for the kind of
workloads Flink is used, I think it is on the decline.
+1 from me
On Tue, Jun 22, 2021 at 11:32 AM Seth Wiesman wrote:
> Sorry if this is a naive question, I don't have any
Hi everyone,
I was thinking today about the migration from akka 2.5.21 that we
currently use to 2.6.x. I saw Chesnay has been thinking about this as
well as he just opened this ticket (1) :)
Besides the general good reasons to upgrade - among others things I'd
add a security fix in akka
62 matches
Mail list logo
