Hi,
I created pull request with the change I proposed in the comment. Could
someone please review it?
https://github.com/apache/flink/pull/9468
--
*Maddila Rishindra Kumar*
*Software Engineer*
*Walmartlabs India*
*Contact No: +919967379528 | Alternate E-mail
ID: rishindra.madd...@walmartlabs.com
Achyuth Narayan Samudrala created FLINK-13768:
-
Summary: Update documentation regarding `path style access` for S3
filesystem implementations
Key: FLINK-13768
URL: https://issues.apache.org/jira/browse
+0 (binding)
I don't think committers should be allowed to approve their own changes. I
would prefer if non-committer contributors can approve committer PRs as
that would encourage more participation in code review and ability to
contribute.
On Fri, Aug 16, 2019 at 9:02 PM Shaoxuan Wang wrote:
Hi,
I would like to be able to edit pages in the Confluence Flink space. Can
someone give me access please?
Thanks
Hi Robert,
Thank you for your reminding! I have added the wiki page[1] for this FLIP.
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-39+Flink+ML+pipeline+and+ML+libs
Robert Metzger 于2019年8月14日周三 下午5:56写道：
> It seems that this FLIP doesn't have a Wiki page yet [1], even though it is
We should investigate the performance regression but regardless the
regression I vote +1
Have verified following things
- Jobs running on YARN x (Session & Per Job) with high-availability enabled.
- Simulate JM and TM failures.
- Simulate temporary network partition.
Best,
tison.
Stephan Ewen
zhijiang created FLINK-13767:
Summary: Migrate isFinished method from AvailabilityListener to
AsyncDataInput
Key: FLINK-13767
URL: https://issues.apache.org/jira/browse/FLINK-13767
Project: Flink
zhijiang created FLINK-13766:
Summary: Refactor the implementation of StreamInputProcessor based
on StreamTaskInput#emitNext
Key: FLINK-13766
URL: https://issues.apache.org/jira/browse/FLINK-13766
Project
zhijiang created FLINK-13765:
Summary: Introduce the InputSelectionHandler for selecting next
input in StreamTwoInputSelectableProcessor
Key: FLINK-13765
URL: https://issues.apache.org/jira/browse/FLINK-13765
A "List Type" sounds like a good direction to me.
The comment on the type system was a bit brief, I agree. The idea is to see
if something like that can ease validation. Especially the correlation
system seems quite complex (proxies to work around order of initialization).
For example, let's assu
zhijiang created FLINK-13764:
Summary: Pass the counter of numRecordsIn into the constructors of
StreamOne/TwoInputProcessor
Key: FLINK-13764
URL: https://issues.apache.org/jira/browse/FLINK-13764
Project
Till Rohrmann created FLINK-13763:
-
Summary: Master build is broken because of wrong Maven version
Key: FLINK-13763
URL: https://issues.apache.org/jira/browse/FLINK-13763
Project: Flink
Issue
Hi all,
I wanted to understand the impact of the hardware we are using for running
our tests. Each travis worker has 2 virtual cores, and 7.5 gb memory [1].
They are using Google Cloud Compute Engine *n1-standard-2* instances.
Running a full "mvn clean verify" takes *03:32 h* on such a machine typ
Hi Stephan,
Thank you for your opinion.
Actually list/composite types are the topics we spent the most of the
time. I understand that from a perspective of a full blown type system,
a field like isList may look weird. Please let me elaborate a bit more
on the reason behind it though. Maybe we wer
zhijiang created FLINK-13762:
Summary: Integrate the implementation of
ForwardingValveOutputHandler for StreamOne/TwoInputProcessor
Key: FLINK-13762
URL: https://issues.apache.org/jira/browse/FLINK-13762
zhihao zhang created FLINK-13761:
Summary: `SplitStream` should be deprecated because
`SplitJavaStream` is deprecated
Key: FLINK-13761
URL: https://issues.apache.org/jira/browse/FLINK-13761
Project: F
Are we fine with the current Netty version, or would be want to bump it?
On Fri, Aug 16, 2019 at 10:30 AM Chesnay Schepler
wrote:
> Hello,
>
> I would like to kick off the next flink-shaded release next week. There
> are 2 ongoing efforts that are blocked on this release:
>
> * [FLINK-13467] J
I could help with that.
On Fri, Aug 16, 2019 at 2:36 PM Robert Metzger wrote:
> Flink 1.9 is feature freezed and almost released.
> I guess it makes sense to update the roadmap on the website again.
>
> Who feels like having a good overview of what's coming up?
>
> On Tue, May 7, 2019 at 4:33 PM
I like the idea of enhancing the configuration and to do early validation.
I feel that some of the ideas in the FLIP seem a bit ad hoc, though. For
example, having a boolean "isList" is a clear indication of not having
thought through the type/category system.
Also, having a more clear category sy
+1
On Sun, Aug 18, 2019 at 3:31 PM Till Rohrmann wrote:
> +1
>
> On Fri, Aug 16, 2019 at 4:54 PM Yu Li wrote:
>
> > Hi All,
> >
> > Since we have reached a consensus in the discussion thread [1], I'd like
> to
> > start the voting for FLIP-50 [2].
> >
> > This vote will be open for at least 72
For reference, this is the JIRA issue about the regression in question:
https://issues.apache.org/jira/browse/FLINK-13752
On Fri, Aug 16, 2019 at 10:57 AM Guowei Ma wrote:
> Hi, till
> I can send the job to you offline.
> It is just a datastream job and does not use TwoInputSelectableStreamTas
+1
On Fri, Aug 16, 2019 at 4:54 PM Yu Li wrote:
> Hi All,
>
> Since we have reached a consensus in the discussion thread [1], I'd like to
> start the voting for FLIP-50 [2].
>
> This vote will be open for at least 72 hours. Unless objection I will try
> to close it by end of Tuesday August 20, 2
Jark Wu created FLINK-13760:
---
Summary: Fix hardcode Scala version dependency in hive connector
Key: FLINK-13760
URL: https://issues.apache.org/jira/browse/FLINK-13760
Project: Flink
Issue Type: Bug
Jark Wu created FLINK-13759:
---
Summary: All builds for master branch are failed during compile
stage
Key: FLINK-13759
URL: https://issues.apache.org/jira/browse/FLINK-13759
Project: Flink
Issue Typ
24 matches
Mail list logo
