[
https://issues.apache.org/jira/browse/FLINK-15517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin closed FLINK-15517.
-----------------------------------
Resolution: Fixed
merged into master by 7513d9b184feffdcb6e0c09d1b74f8de21a98e81
merged into 1.10 by a6023e6953189ece1bb8fbb7bc3e117172ad5264
> Use back 'network' in 'shuffle' memory config option names
> ----------------------------------------------------------
>
> Key: FLINK-15517
> URL: https://issues.apache.org/jira/browse/FLINK-15517
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration, Runtime / Task
> Affects Versions: 1.10.0
> Reporter: Andrey Zagrebin
> Assignee: Andrey Zagrebin
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The issue is based on the discussion outcome on [Dev
> ML|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Some-feedback-after-trying-out-the-new-FLIP-49-memory-configurations-td36129.html].
> As there is no strong consensus about using new 'shuffle' naming for memory
> config options. We decided to fallback to the the existing naming and use
> 'network' instead of 'shuffle'. We still keeping the new naming convention
> with prefix 'taskmanager.memory.*'.
> Basically, we just need to rename 'taskmanager.memory.shuffle.*' to
> 'taskmanager.memory.network.*' as 'shuffle' naming has never been released.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
