Fin-chan created FLINK-19058:
Summary: Dataset transformations document page error
Key: FLINK-19058
URL: https://issues.apache.org/jira/browse/FLINK-19058
Project: Flink
Issue Type: Bug
Welcome Kartik and Muhammad! Thanks in advance for helping improve Flink
documentation.
Best,
Jark
On Thu, 27 Aug 2020 at 03:59, Till Rohrmann wrote:
> Welcome Muhammad and Kartik! Thanks a lot for helping us with improving
> Flink's documentation.
>
> Cheers,
> Till
>
> On Wed, Aug 26, 2020
Hi everyone,
According to the feedback, it seems adding `isTemporary` to factory context
is the preferred way to fix the issue. I'll go ahead and make the change if
no one objects.
On Tue, Aug 25, 2020 at 5:36 PM Rui Li wrote:
> Hi,
>
> Thanks everyone for your inputs.
>
> Temporary hive table
Xintong Song created FLINK-19057:
Summary: Avoid usage of GlobalConfiguration in ResourceManager
Key: FLINK-19057
URL: https://issues.apache.org/jira/browse/FLINK-19057
Project: Flink
Issue
Chesnay Schepler created FLINK-19056:
Summary: Investigate multipart upload performance regression
Key: FLINK-19056
URL: https://issues.apache.org/jira/browse/FLINK-19056
Project: Flink
Welcome Muhammad and Kartik! Thanks a lot for helping us with improving
Flink's documentation.
Cheers,
Till
On Wed, Aug 26, 2020 at 7:32 PM Konstantin Knauf wrote:
> Welcome Kartik & Muhammad! Looking very much forward to your contributions
> :)
>
> On Wed, Aug 26, 2020 at 5:52 PM Kartik Khare
Welcome Kartik & Muhammad! Looking very much forward to your contributions
:)
On Wed, Aug 26, 2020 at 5:52 PM Kartik Khare wrote:
> Hi all,
> It's a great opportunity to get to work with you guys. I have always
> admired Flink's performance and simplicity and have been looking forward to
>
Hi all,
It's a great opportunity to get to work with you guys. I have always
admired Flink's performance and simplicity and have been looking forward to
contribute more.
Looking forward to exciting next 3 months.
Regards,
Kartik
On Wed, 26 Aug 2020, 14:42 Marta Paes Moreira, wrote:
> Hi,
I added more changes to the FLIP to try and address comments.
You can see the changes from the last version here:
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=158866741=31=27
If no-one objects anymore I would like to proceed to a VOTE soon.
Best,
Aljoscha
On
Matthias created FLINK-19055:
Summary: MemoryManagerSharedResourcesTest contains three tests
running extraordinary long
Key: FLINK-19055
URL: https://issues.apache.org/jira/browse/FLINK-19055
Project:
Dian Fu created FLINK-19054:
---
Summary: KafkaTableITCase.testKafkaSourceSink hangs
Key: FLINK-19054
URL: https://issues.apache.org/jira/browse/FLINK-19054
Project: Flink
Issue Type: Bug
Thanks ZhuZhu for managing this release and everyone who contributed to this.
Best,
Pengcheng
在 2020/8/26 下午7:06，“Congxian Qiu” 写入:
Thanks ZhuZhu for managing this release and everyone else who contributed
to this release!
Best,
Congxian
Xingbo Huang 于2020年8月26日周三
Thanks ZhuZhu for being the release manager and everyone who contributed to
this release.
Best,
Leonard
liugh created FLINK-19053:
-
Summary: Flink Kafka Connector Dependency Error
Key: FLINK-19053
URL: https://issues.apache.org/jira/browse/FLINK-19053
Project: Flink
Issue Type: Bug
Thanks ZhuZhu for managing this release and everyone else who contributed
to this release!
Best,
Congxian
Xingbo Huang 于2020年8月26日周三 下午1:53写道：
> Thanks Zhu for the great work and everyone who contributed to this release!
>
> Best,
> Xingbo
>
> Guowei Ma 于2020年8月26日周三 下午12:43写道：
>
>> Hi,
>>
Thanks for the quick response.
*Job prioritization, Allocation IDs, Minimum resource
requirements, SlotManager Implementation Plan:* Sounds good to me.
*FLIP-56*
Good point about the trade-off. I believe maximum resource utilization and
quick deployment are desired in different scenarios. E.g.,
Roman Grebennikov created FLINK-19052:
-
Summary: Performance issue with PojoSerializer
Key: FLINK-19052
URL: https://issues.apache.org/jira/browse/FLINK-19052
Project: Flink
Issue Type:
Hi devs,
I'd like to bring the discussion over FLIP-141[1], which proposes how
managed memory should be shared by various use cases within a slot. This is
an extension to FLIP-53[2], where we assumed that RocksDB state backend and
batch operators are the only use cases of managed memory for
Thank you Xintong for your questions!
Job prioritization
Yes, the job which declares it's initial requirements first is prioritized.
This is very much for simplicity; for example this avoids the nasty case
where all jobs get some resources, but none get enough to actually run
the job.
Hi, Everyone!
I'd like to officially welcome the applicants that were selected to work
with the Flink community for this year's Google Season of Docs (GSoD)
[1]: *Kartik
Khare* and *Muhammad Haseeb Asif*!
- Kartik [2] is a software engineer at Walmart Labs and a regular
contributor to
Thanks for preparing the FLIP and driving this discussion, @Chesnay & @Till.
I really like the idea. I see a great value in the proposed declarative
resource management, in terms of flexibility, usability and efficiency.
I have a few comments and questions regarding the FLIP design. In general,
Pua created FLINK-19051:
---
Summary: Exception message should be reserved in log When the Job
Manager failed
Key: FLINK-19051
URL: https://issues.apache.org/jira/browse/FLINK-19051
Project: Flink
22 matches
Mail list logo
