[
https://issues.apache.org/jira/browse/FLINK-15198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019373#comment-17019373
]
Andrey Zagrebin commented on FLINK-15198:
-----------------------------------------
[~yanghua]
Technically, this Mesos options class is even @Internal and can change w/o any
notice. On the other hand, this class is user facing API, IMO, and I would
suggest to see it as at least @PublicEvolving. I have not found any detailed
deprecation guide or bylaws (it could be something for a ML discussion).
>From @PublicEvolving jdocs, it says that the @PublicEvolving can change across
>versions.
>From @Public jdocs, it says that the @Public can change across only major
>versions.
In general, I would suggest to go through the deprecation process where the
user facing API is kept at least for one release cycle atm because this gives a
notice to the users.
> Remove deprecated mesos.resourcemanager.tasks.mem in 1.11
> ---------------------------------------------------------
>
> Key: FLINK-15198
> URL: https://issues.apache.org/jira/browse/FLINK-15198
> Project: Flink
> Issue Type: Task
> Components: Deployment / Mesos
> Affects Versions: 1.11.0
> Reporter: Andrey Zagrebin
> Assignee: ptmagic
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In FLINK-15082, we deprecated 'mesos.resourcemanager.tasks.mem' in favour of
> the new unified option 'taskmanager.memory.total-process.size' from FLIP-49.
> We should remove it now in 1.11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
