Jiayong Mo created FLINK-11169:
--
Summary: [hotfix][runtime] fix the problem of not being reloaded
for jobmanager's log after clicking the refresh button in web ui
Key: FLINK-11169
URL:
Thank you, Timo. I'll read the guidelines carefully.
谢谢~
五藏
--
发件人:Timo Walther
发送时间:2018年12月14日(星期五) 20:26
收件人:dev
主 题:Re: Apply for flink contributor permission
Hi Tony,
I gave you contributor permissions. Please also have a
Chesnay Schepler created FLINK-11168:
Summary: LargePlanTest times out on Travis
Key: FLINK-11168
URL: https://issues.apache.org/jira/browse/FLINK-11168
Project: Flink
Issue Type: Bug
I will cancel the RC and revert the commit.
On 14.12.2018 15:29, Timo Walther wrote:
Hi everyone,
I just noticed that FLINK-9555 [1] has been accidently merged to the
release-1.7 branch. How do we want to deal with that?
The Scala Shell is not a super crucial Flink feature. But this commit
Hi everyone,
I just noticed that FLINK-9555 [1] has been accidently merged to the
release-1.7 branch. How do we want to deal with that?
The Scala Shell is not a super crucial Flink feature. But this commit
does not only introduce a new feature and adds new dependencies but also
introduces a
Hi Xianda, hi Shaoxuan,
I'd be in favor of option (1). There is great potential in Beam and Flink
joining forces on this one. Here's why:
The Beam project spent at least a year developing a portability layer with a
reasonable amount of people working on it. Developing a new portability layer
Can confirm they still go to the main comment section.
Would be great if we could send them to the Work Log instead. We do that for the
Beam JIRA project and it has proven very useful for reducing noise.
Thanks,
Max
On 13.12.18 22:15, Tzu-Li Chen wrote:
hmm..then what is it
Chesnay
I have pushed this fix to the release-1.5 branch:
https://issues.apache.org/jira/browse/FLINK-10566
Would be great if we could include it because it has been blocking some
pipelines on the Beam side.
Thanks,
Max
On 13.12.18 20:22, Chesnay Schepler wrote:
FLINK-11023: will not be fixed for
Hi Chesnay,
Just saw this. I had unarchived the version because I thought it had been
archived accidentally. I have archived it again.
I hope it is ok to include this fix:
https://issues.apache.org/jira/browse/FLINK-10566
Otherwise, feel free to move it to 1.7.2.
Thanks,
Max
On 13.12.18
Hi everyone,
Please review and vote on the release candidate #1 for the version
1.7.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
Hi Tony,
I gave you contributor permissions. Please also have a look at our
contributor guidelines before you start working on issues:
https://flink.apache.org/contribute-code.html
Regards,
Timo
Am 14.12.18 um 03:01 schrieb 宋辛童(五藏):
Hi there,
Could anyone kindly give me the contributor
Thank you. I'll read contributing code carefully and keep in mind that :)
Timo Walther 于2018年12月14日周五 下午8:15写道:
> Hi Shengyang,
>
> I gave you contributor permissions. Please also have a look at our
> contributor guidelines:
>
> https://flink.apache.org/contribute-code.html
>
> Regards,
> Timo
Hi Shengyang,
I gave you contributor permissions. Please also have a look at our
contributor guidelines:
https://flink.apache.org/contribute-code.html
Regards,
Timo
Am 14.12.18 um 11:47 schrieb Shengyang Sha:
Hi,
I've been interested in flink for a long time and have worked on a few
Hi all,
I think we should discuss what we consider an MVP DDL. For me, an MVP
DDL was to just focus on a CREATE TABLE statement. It would be great to
come up with a solution that finally solves the issue of connecting
different kind of systems. One reason why we postponed DDL statements
for
Improvements should be discussed on the mailing list as well, so that is
the right point to start.
For bug fixes, please open a JIRA issue - you should be able to do this
even now.
On Fri, Dec 14, 2018 at 11:42 AM 杨弢 wrote:
> Hi, Stephan Ewen:
> Thanks for the reply!
> Sorry for not being
Hi,
I've been interested in flink for a long time and have worked on a few
internal features mainly in flink-runtime. I'd like to apply for
contributor permission so that I could join feature development or bugfixes
in flink. My jira account ID is ssy .
Best regards,
Shengyang Sha
Congxian Qiu created FLINK-11167:
Summary: Optimize RocksDBList#put for no empty input
Key: FLINK-11167
URL: https://issues.apache.org/jira/browse/FLINK-11167
Project: Flink
Issue Type:
Tony Xintong Song created FLINK-11166:
-
Summary: Slot Placement Constraint
Key: FLINK-11166
URL: https://issues.apache.org/jira/browse/FLINK-11166
Project: Flink
Issue Type: New Feature
Zhu Zhu created FLINK-11165:
---
Summary: Refine the deploying log for easier finding of task
locations
Key: FLINK-11165
URL: https://issues.apache.org/jira/browse/FLINK-11165
Project: Flink
Issue
Tzu-Li (Gordon) Tai created FLINK-11164:
---
Summary: Refreshing expired shard iterator fails if no records
were retrieved from shard since ShardConsumer was started in
FlinkKinesisConsumer
Key: FLINK-11164
20 matches
Mail list logo