Benchao Li created FLINK-11722:
--
Summary: Fix the outdated java doc in AkkaRpcServiceUtils
Key: FLINK-11722
URL: https://issues.apache.org/jira/browse/FLINK-11722
Project: Flink
Issue Type: Impr
zhijiang created FLINK-11723:
Summary: Remove KvState related components from NetworkEnvironment
Key: FLINK-11723
URL: https://issues.apache.org/jira/browse/FLINK-11723
Project: Flink
Issue Type:
zhijiang created FLINK-11721:
Summary: Remove IOMode from NetworkEnvironment
Key: FLINK-11721
URL: https://issues.apache.org/jira/browse/FLINK-11721
Project: Flink
Issue Type: Sub-task
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is derek.wq
Derek Wu
Thank you&Best Regards
Hi Stephan,
Thanks for summarizing the great roadmap! It is very helpful for users and
developers to track the direction of Flink.
+1 for putting the roadmap on the website and update it per release.
Besides, would be great if the roadmap can add the UpsertSource
feature(maybe put it under 'Batch
Hi everyone,
I’m happy to announce that we have unanimously approved this release
candidate to be the 1.6.4 release.
There are 8 approving votes, 3 of which are binding:
* Hequn (non-binding)
* Dian (non-binding)
* Vino (non-binding)
* Jark (non-binding)
* Fabian (binding)
* Wei (non-binding)
*
+1 (binding)
- "mvn clean verify" ran successfully (I ran into an issue with the ES5
connector on Google Cloud, but that's only a test instability that existed
already in 1.6.2) https://issues.apache.org/jira/browse/FLINK-11720
- checked staging repo contents, validated a signature there
- Ran the
Hi Stephan,
Yes. I completely agree. Jincheng & Jark gave some very valuable feedbacks
and suggestions and I think we can definitely move the conversation forward
to reach a more concrete doc first before we put in to the roadmap. Thanks
for reviewing it and driving the roadmap effort!
--
Rong
O
Hi All,
Thanks for sharing feedbacks for the window optimization design doc and on
the discussion JIRAs @Jincheng, @Kurt, @Jark and @Fabian. These are very
valuable feedbacks and we will try to incorporate them in the next step.
There were several revision done for the current design doc, and sev
Hi Shaoxuan!
I think adding the web UI improvements makes sense - there is not much open
to discuss there. Will do that.
For the machine learning improvements - that is a pretty big piece and I
think the discussions are still ongoing. I would prefer this to advance a
bit before adding it to the r
Hi Rong Rong!
I would add the security / kerberos threads to the roadmap. They seem to be
advanced enough in the discussions so that there is clarity what will come.
For the window operator with slicing, I would personally like to see the
discussion advance and have some more clarity and consensu
Robert Metzger created FLINK-11720:
--
Summary: ES5: ElasticsearchSinkITCase failing
Key: FLINK-11720
URL: https://issues.apache.org/jira/browse/FLINK-11720
Project: Flink
Issue Type: Task
Till Rohrmann created FLINK-11719:
-
Summary: Remove JobMaster#start(JobMasterId) and #suspend
Key: FLINK-11719
URL: https://issues.apache.org/jira/browse/FLINK-11719
Project: Flink
Issue Type
Till Rohrmann created FLINK-11718:
-
Summary: Add onStart method to RpcEndpoint which is run in the
actor's main thread
Key: FLINK-11718
URL: https://issues.apache.org/jira/browse/FLINK-11718
Project:
Hi Chesnay,
Thanks for the comments. I think this is worthy of a FLIP because it is
public API. According to the FLIP description a FlIP is required in case of:
- Any change that impacts the public interfaces of the project
and the following entry is found in the definition of "public interfa
Then the respective target components should have a "split
Job-Submission" migration path attached to them.
None of the 3 components you just listed have this.
On 21.02.2019 16:10, Robert Metzger wrote:
Thank you for the minor issues you've found. I addressed them:
https://cwiki.apache.org/conf
Thank you for the minor issues you've found. I addressed them:
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=103089605&selectedPageVersions=6&selectedPageVersions=5
@Chesnay: Regarding the "Job-Submission": I quickly looked over the
tickets. Many of them clearly fit in
Hey guys,
Thanks for your comments and sorry for the late reply.
Beam Python API and Flink Python TableAPI describe the DAG/pipeline in
different manners. We got a chance to communicate with Tyler Akidau (from
Beam) offline, and explained why the Flink tableAPI needs a specific design
for python, r
+1 (non-binding)
- compiled from source
- started standalone cluster and tried a WordCount example.
Best,
Wei
> 在 2019年2月20日，上午5:59，Fabian Hueske 写道：
>
> +1 (binding)
>
> * checked commit diff since Flink 1.6.3, did not find any added non-AL2
> dependencies
> * checked signatures and hashes
Jark Wu created FLINK-11717:
---
Summary: Translate the "Material" page into Chinese
Key: FLINK-11717
URL: https://issues.apache.org/jira/browse/FLINK-11717
Project: Flink
Issue Type: Sub-task
+1
- checked release notes
- no critical issues were addressed in 1.7.2 that were marked as
affecting 1.6.X but not fixed for it
- source release
- contains no binaries
- contains no 1.6-SNAPSHOT references
- binary release
- no examples appear to be missing
- started a cluster;
Regarding 2) It doesn't make sense to investigate this as part of this
FLIP. This is something that could be of interest for the entire metric
system, and should be designed for as such.
Regarding the proposal as a whole:
Histogram metrics shall not be added to the core of Flink. They are
sig
Hi,
Ad 1. In general I undestand and I agree. But those particular metrics
(latency, fetchLatency), right now would only be reported if user uses
KafkaConsumer with internal timestampAssigner with StreamCharacteristic
set to EventTime, right? That sounds like a very specific case. I am not
sure if
Probably I am bit late to the party, but I just started using the Flinkbot.
A big +1 for having 3 states for each step. (Pending, Approved,
Rejected). Right now it is impossible to say
that I checked e.g. consensus and decided that the feature requires
further discussion.
Best,
Dawid
On 21/02
Alex created FLINK-11716:
Summary: Introduce Task Manager configuration option to customize
address binding mechanism
Key: FLINK-11716
URL: https://issues.apache.org/jira/browse/FLINK-11716
Project: Flink
godfrey he created FLINK-11715:
--
Summary: Add optimize program to organize optimization phases
Key: FLINK-11715
URL: https://issues.apache.org/jira/browse/FLINK-11715
Project: Flink
Issue Type:
Hi Dawid,
Thanks for the feedback. That makes sense to me. There are two cases to be
addressed.
1. The metrics are supposed to be a guidance. It is likely that a connector
only supports some but not all of the metrics. In that case, each connector
implementation should have the freedom to decide
Thanks Kostas!
On Mon, Feb 18, 2019 at 5:10 PM Kostas Kloudas
wrote:
> Hi Padarn,
>
> This is the jira issue: https://issues.apache.org/jira/browse/FLINK-11187
> and the fix, as you can see, was first included in version 1.7.2.
>
> Cheers,
> Kostas
>
> On Mon, Feb 18, 2019 at 3:49 AM Padarn Wil
godfrey he created FLINK-11714:
--
Summary: Add cost model for both batch and streaming
Key: FLINK-11714
URL: https://issues.apache.org/jira/browse/FLINK-11714
Project: Flink
Issue Type: New Featu
Gary Yao created FLINK-11713:
Summary: Remove legacy mode from documentation
Key: FLINK-11713
URL: https://issues.apache.org/jira/browse/FLINK-11713
Project: Flink
Issue Type: Improvement
godfrey he created FLINK-11712:
--
Summary: Add cost model for both batch and streaming
Key: FLINK-11712
URL: https://issues.apache.org/jira/browse/FLINK-11712
Project: Flink
Issue Type: New Featu
godfrey he created FLINK-11711:
--
Summary: Add table and column stats
Key: FLINK-11711
URL: https://issues.apache.org/jira/browse/FLINK-11711
Project: Flink
Issue Type: New Feature
Comp
TisonKun created FLINK-11710:
Summary: Refactor SimpleSlotProvider to TestingLogicalSlotProvider
Key: FLINK-11710
URL: https://issues.apache.org/jira/browse/FLINK-11710
Project: Flink
Issue Type:
Hi,
Generally I like the idea of having a unified, standard set of metrics
for all connectors. I have some slight concerns about fetchLatency and
latency though. They are computed based on EventTime which is not a
purely technical feature. It depends often on some business logic, might
be absent o
34 matches
Mail list logo
