[
https://issues.apache.org/jira/browse/HADOOP-14957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213309#comment-16213309
]
Andrew Wang commented on HADOOP-14957:
--------------------------------------
Sorry, hit reply too soon. My closing thought is that we need to purge Guava
from our API to fix cross-compatibility between our unshaded and shaded
clients. We want to really be encouraging usage of the shaded client, and if we
don't do this, it's a major usability concern.
Finally, we also have the option of providing *both* APIs. The Guava-Optional
API will still be different between the shaded and unshaded clients, but the
Java-Optional one will be fine. This provides a more graceful migration path.
I'm okay with either, though more opinions would of course be welcome.
> ReconfigurationTaskStatus is exposing guava Optional in its public api
> ----------------------------------------------------------------------
>
> Key: HADOOP-14957
> URL: https://issues.apache.org/jira/browse/HADOOP-14957
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: common
> Affects Versions: 3.0.0-beta1
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Attachments: HADOOP-14957.prelim.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
