dianfu commented on pull request #329:
URL: https://github.com/apache/flink-web/pull/329#issuecomment-619327260
Merged via af2d8de132b73f0dae6fd88912fe1c92202f3efe
This is an automated message from the Apache Git Service.
To
Hi Guys,
I want to contribute to Apache Flink.
Would you please give me the permission as a contributor?
My JIRA ID is ziping.
Hi Xuannan,
If user submits Job 1 and generated a cached intermediate result. And later
on, user submitted job 2 which should ideally use the intermediate result.
In that case, if job 2 failed due to missing the intermediate result, Job 2
should be retried with its full DAG. After that when Job 2
Hi everyone,
Please review and vote on the release candidate #1 for version 1.10.1, 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],
*
carp84 opened a new pull request #330:
URL: https://github.com/apache/flink-web/pull/330
Adds release announcement and download link for 1.10.1
Dates on announcements are still TBD and should be updated accordingly once
release happens.
Stephan Ewen created FLINK-17376:
Summary: Remove deprecated state access methods
Key: FLINK-17376
URL: https://issues.apache.org/jira/browse/FLINK-17376
Project: Flink
Issue Type:
I'll turn this into a ticket for 1.11 then.
Thanks!
On Thu, Apr 23, 2020 at 4:13 PM Aljoscha Krettek
wrote:
> Definitely +1! I'm always game for decreasing the API surface if it
> doesn't decrease functionality.
>
> Aljoscha
>
> On 23.04.20 14:18, DONG, Weike wrote:
> > Hi Stephan,
> >
> > +1
Thanks for the update Piotr.
Cheers,
Till
On Fri, Apr 24, 2020 at 4:42 PM Piotr Nowojski wrote:
> Hi community,
>
> It has been more than 6 weeks since the previous announcement and as we are
> approaching the expected feature freeze we would like to share the Flink
> 1.11 status update with
Hi Manish,
the label the Flink community uses is "starter". Be aware that it has not
been used very consistently in the past, though.
Cheers,
Till
On Fri, Apr 24, 2020 at 4:12 PM Manish G
wrote:
> Are there tags for jira issues which can help in identifying issues
> which beginners can start
Hi community,
It has been more than 6 weeks since the previous announcement and as we are
approaching the expected feature freeze we would like to share the Flink
1.11 status update with you.
Initially we were aiming for the feature freeze to happen in late April
(now), however it was recently
Are there tags for jira issues which can help in identifying issues
which beginners can start with?
Thanks.
Hi Till,
Looking forward too ...
Thanks
Etienne
On 24/04/2020 15:09, Till Rohrmann wrote:
Hi Etienne,
welcome to the Flink community. Looking forward to working with you on
Flink :-)
Cheers,
Till
On Fri, Apr 24, 2020 at 11:20 AM Etienne Chauchot
wrote:
Hi everyone,
Let me introduce
Robert Metzger created FLINK-17375:
--
Summary: Clean up CI system related scripts
Key: FLINK-17375
URL: https://issues.apache.org/jira/browse/FLINK-17375
Project: Flink
Issue Type: Sub-task
Robert Metzger created FLINK-17374:
--
Summary: Remove travis-related files
Key: FLINK-17374
URL: https://issues.apache.org/jira/browse/FLINK-17374
Project: Flink
Issue Type: Sub-task
+1 for "slim" and "fat" solution. One comment about the fat one, I think we
need to
put all needed jars into /lib (or /plugins). Put jars into /opt and relying
on users moving
them from /opt to /lib doesn't really improve the out-of-box experience.
Best,
Kurt
On Fri, Apr 24, 2020 at 8:28 PM
Hi Etienne,
welcome to the Flink community. Looking forward to working with you on
Flink :-)
Cheers,
Till
On Fri, Apr 24, 2020 at 11:20 AM Etienne Chauchot
wrote:
> Hi everyone,
>
> Let me introduce myself, I'm Etienne Chauchot, I'm an Apache Beam
> committer and a PMC member and I would like
Timo Walther created FLINK-17373:
Summary: Support the NULL type for function calls
Key: FLINK-17373
URL: https://issues.apache.org/jira/browse/FLINK-17373
Project: Flink
Issue Type:
re (1): I don't know about that, probably the people that did the
metrics reporter plugin support had some thoughts about that.
re (2): I agree, that's why I initially suggested to split it into
"slim" and "fat" because our current "medium fat" selection of jars in
Flink dist does not serve
Hi Stephan,
I fully agree with what you said. Also as far as I can tell what was
suggested in the FLIP-124 does not contradict with what you are saying.
Let me clarify it a bit if it is not clear in the document.
Current implementations of Kafka and Kinesis do the deserialization
outside of the
Hi all
I'd like to start the discussion about Prometheus labelNames.
We need to add some custom labels on Prometheus, so we can query by them. We
can add groupingKey to PrometheusPushGatewayReporter in version 1.10, but not
in PrometheusReporter. Can we add abstract addLabels method on
Till Rohrmann created FLINK-17372:
-
Summary: SlotManager should expose total required resources
Key: FLINK-17372
URL: https://issues.apache.org/jira/browse/FLINK-17372
Project: Flink
Issue
Kurt Young created FLINK-17371:
--
Summary: Failed to cast decimal from string or double
Key: FLINK-17371
URL: https://issues.apache.org/jira/browse/FLINK-17371
Project: Flink
Issue Type:
Hi everyone,
Let me introduce myself, I'm Etienne Chauchot, I'm an Apache Beam
committer and a PMC member and I would like to start working on Flink as
well.
For now I only did 3 simple Flink PRs but that will grow :)
https://github.com/apache/flink/pull/11886
Dear All,
I want to propose a change to the current RabbitMQ connector.
Currently the RMQSource is extracting the body of the message which is a
byte array and pass it to a an instance of a user implementation of the
DeserializationSchema class to deserialize the body of the message. It also
Timo Walther created FLINK-17370:
Summary: Ensure deterministic type inference extraction
Key: FLINK-17370
URL: https://issues.apache.org/jira/browse/FLINK-17370
Project: Flink
Issue Type:
Hi Becket,
The intermediate result will indeed be automatically re-generated by
resubmitting the original DAG. And that job could fail as well. In that
case, we need to decide if we should resubmit the original DAG to
re-generate the intermediate result or give up and throw an exception to
the
谢谢
在 2020-04-24 16:09:04,"Caizhi Weng" 写道:
>Hi shx,
>
>Glad to hear that you're willing to contribute! Flink currently does not
>have contributor permissions. To contribute to an issue, just reply to the
>issue with your thoughts and create a PR after the discussion with
>community about the
Hi Xuannan,
I am not entirely sure if I understand the cases you mentioned. The users
> can use the cached table object returned by the .cache() method in other
> job and it should read the intermediate result. The intermediate result can
> gone in the following three cases: 1. the user
Hi shx,
Glad to hear that you're willing to contribute! Flink currently does not
have contributor permissions. To contribute to an issue, just reply to the
issue with your thoughts and create a PR after the discussion with
community about the issue.
shx <17611022...@163.com> 于2020年4月24日周五
zl created FLINK-17368:
--
Summary: exception message in PrometheusPushGatewayReporter
Key: FLINK-17368
URL: https://issues.apache.org/jira/browse/FLINK-17368
Project: Flink
Issue Type: Bug
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is hongxiao
Hi Becket,
Thanks for the comments.
On Fri, Apr 24, 2020 at 9:12 AM Becket Qin wrote:
> Hi Xuannan,
>
> Thanks for picking up the FLIP. It looks good to me overall. Some quick
> comments / questions below:
>
> 1. Do we also need changes in the Java API?
>
Yes, the public interface of Table
Flavio Pompermaier created FLINK-17366:
--
Summary: Implement listViews
Key: FLINK-17366
URL: https://issues.apache.org/jira/browse/FLINK-17366
Project: Flink
Issue Type: Sub-task
Chesnay Schepler created FLINK-17367:
Summary: Support generating dockerfiles against custom URL
Key: FLINK-17367
URL: https://issues.apache.org/jira/browse/FLINK-17367
Project: Flink
Chesnay Schepler created FLINK-17365:
Summary: Update Dockerfiles to 1.9.3
Key: FLINK-17365
URL: https://issues.apache.org/jira/browse/FLINK-17365
Project: Flink
Issue Type: Improvement
+1
On Thu, Apr 23, 2020 at 4:10 PM Stephan Ewen wrote:
> Hi all!
>
> I want to bring up a discussion about when we want to do the feature freeze
> for 1.11.
>
> When kicking off the release cycle, we tentatively set the date to end of
> April, which would be in one week.
>
> I can say from the
36 matches
Mail list logo