[
https://issues.apache.org/jira/browse/FLINK-10275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602588#comment-16602588
]
ASF GitHub Bot commented on FLINK-10275:
----------------------------------------
TisonKun commented on issue #6643: [FLINK-10275] StreamTask support object reuse
URL: https://github.com/apache/flink/pull/6643#issuecomment-418236948
This pull request would affect reusing of object from network, according to
[FLIP-21](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=71012982),
it is another reuse aspect from current `ExecutionConfig#isObjectReuseEnable`
configuration.
Travis fails on `TableSinkITCase#testAppendSinkOnAppendTableForInnerJoin`
which is because of mutating inputValue. We need a extra config to switch
network aspect object reuse. Still digging...
Suggestions are welcome :-)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> StreamTask support object reuse
> -------------------------------
>
> Key: FLINK-10275
> URL: https://issues.apache.org/jira/browse/FLINK-10275
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 1.7.0
> Reporter: 陈梓立
> Assignee: 陈梓立
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> StreamTask support efficient object reuse. The purpose behind this is to
> reduce pressure on the garbage collector.
> All objects are reused, without backup copies. The operators and UDFs must be
> careful to not keep any objects as state or not to modify the objects.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
