Hi biao, thanks for your feedbacks:
Actually, the runtime source partition of runtime is similar to split, which
concerns data reading, parallelism and fault tolerance, all the runtime
concepts.
While table partition is only a virtual concept. Users are more likely to
choose which partition to
+1 to rethink
Best,
Jingsong Lee
--
From:Stephan Ewen
Send Time:2019年9月10日(星期二) 15:40
To:dev
Cc:JingsongLee
Subject:Re: [DISCUSS] Support notifyOnMaster for notifyCheckpointComplete
Hi all!
I think it would be time to rethink
HI Bowen,
Thank you for sharing your research summaries. The concerns you raised
about the modular approach are very valuable and practical. Here are some
of my thoughts..
1. Naming conflicts and resolution. Naming conflicts is likely, and as you
suggested, the resolution can be just based on
Till Rohrmann created FLINK-14047:
-
Summary: Hide secret values when displaying user
configuration/global job parameters in web UI
Key: FLINK-14047
URL: https://issues.apache.org/jira/browse/FLINK-14047
+1 (binding)
- verified checksums and signatures
- no binary files in source release
- built Flink from source release with Scala 2.12, running all tests
- Verified that no new dependencies have been added
- Executed simple example jobs locally (worked)
Cheers,
Till
On Tue, Sep 10, 2019 at 8:00
hailong wang created FLINK-14046:
Summary: DDL property 'format.fields.#.type' should ignore case
Key: FLINK-14046
URL: https://issues.apache.org/jira/browse/FLINK-14046
Project: Flink
Gary Yao created FLINK-14045:
Summary: Rewrite DefaultExecutionSlotAllocator to use
SlotProviderStrategy
Key: FLINK-14045
URL: https://issues.apache.org/jira/browse/FLINK-14045
Project: Flink
Arvid Heise created FLINK-14044:
---
Summary: Reducing synchronization in AsyncWaitOperator
Key: FLINK-14044
URL: https://issues.apache.org/jira/browse/FLINK-14044
Project: Flink
Issue Type:
Till Rohrmann created FLINK-14043:
-
Summary: SavepointMigrationTestBase is super slow
Key: FLINK-14043
URL: https://issues.apache.org/jira/browse/FLINK-14043
Project: Flink
Issue Type: Bug
Yuval Itzchakov created FLINK-14042:
---
Summary: Different RelDataTypes generated for same
TemporalTableFunction
Key: FLINK-14042
URL: https://issues.apache.org/jira/browse/FLINK-14042
Project: Flink
Hi Till,
Thanks for your quick reply. I'd like to narrow the intention of this
thread as I posted above
>Well, I see your concerns on replace existing stable services hurriedly
with
a new implementation. Here I list the pros and cons of this replacement. If
we
agree that it does good I can
I want to implement grouping set in stream. I am new to flink sql. I
want to find a example to teach me how to self define rule and
implement corresponding operator. Can anyone give me any suggestion?
Hi all!
Nice to see this lively discussion about the Pulsar connector.
Some thoughts on the open questions:
## Contribute to Flink or maintain as a community package
Looks like the discussion is more going towards contribution. I think that
is good, especially if we think that we want to build
Hi Tison,
thanks for the detailed response. I put some comments inline:
On Tue, Sep 10, 2019 at 10:51 AM Zili Chen wrote:
> Hi Till,
>
> Thanks for your reply. I agree point 3 and 4 in your email worth a
> separated
> thread to discuss. Let me answer your questions and concerns in point 1 and
TisonKun created FLINK-14041:
Summary: Refactor LeaderRetrievalServiceHostnameResolutionTest and
remove StandaloneUtils
Key: FLINK-14041
URL: https://issues.apache.org/jira/browse/FLINK-14041
Project:
Hi everyone!
Thanks for your attention and the promotion of this work.
We will prepare a FLIP as soon as possible for more specific discussions.
For FLIP-27, it seems that we have not reached a consensus. Therefore,
I will explain all the functionalities of the existing connector in
the FLIP
Zhu Zhu created FLINK-14040:
---
Summary: Enable a cron job to run MiniCluster tests for schedulerNG
Key: FLINK-14040
URL: https://issues.apache.org/jira/browse/FLINK-14040
Project: Flink
Issue Type:
Hi Till,
Thanks for your reply. I agree point 3 and 4 in your email worth a separated
thread to discuss. Let me answer your questions and concerns in point 1 and
2
respectively.
1.Lifecycle of LeaderServer and requirement to implement it
LeaderServer starts on cluster entrypoint and its
Hi Jan,
sorry for my late response. I think the main concern about using the
context class loader is the unpredictability and magic it adds to a
component where you actually don't wanna be surprised. Moreover, if we now
add support for the context class loader, then at a later time another
Thanks Chesnay for drafting the FLIP and starting this discussion.
I have a couple of comments:
* I know that I've also coined the terms global/local result partition but
maybe it is not the perfect name. Maybe we could rethink the terminology
and call them persistent result partitions?
* Nit: I
Ying Xu created FLINK-14039:
---
Summary: Flink Kinesis consumer: configurable per-shard
consumption rate when running in adaptive mode
Key: FLINK-14039
URL: https://issues.apache.org/jira/browse/FLINK-14039
Hi all!
I think it would be time to rethink the Sink API as a whole, like we did
with the Source API in FLIP-27.
It would be nice to have proper design that handles all this consistently,
rather than adding one more hook.
For example:
- For batch, you can already use the existing "finalize on
Hi Jingsong,
Thank you for bringing this discussion. Since I don't have much experience
of Flink table/SQL, I'll ask some questions from runtime or engine
perspective.
> ... where we describe how to partition support in flink and how to
integrate to hive partition.
FLIP-27 [1] introduces
+1 (binding)
- build from source and passed all tests locally
- checked the difference between 1.8.1 and 1.8.2, no legal risk found
- went through all commits checked in between 1.8.1 and 1.8.2, make
sure all the issues set the proper "fixVersion" property
Best,
Kurt
On Mon, Sep 9, 2019 at
24 matches
Mail list logo
