[
https://issues.apache.org/jira/browse/HADOOP-14384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998715#comment-15998715
]
Anu Engineer commented on HADOOP-14384:
---------------------------------------
[~eddyxu] Thanks for comments. May be I was not very clear with my questions.
Would you please take a little time and share your thoughts on each of these
points below. Here are my specific questions.
* Why make this private if we are not planning to ship this ? In other words,
but I still fail to see why we are making this private. The original issue was
that it was a good concept badly executed. Does not that stand even if we make
this private ?
* Given the comments on the original JIRA, I would presume that this is going
to be reworked to an extent ?
bq. This new Builder interface is part of larger effort in EC development in
trunk. So it is desired to be kept in trunk
This is what I am trying to understand, I am all for keeping this in trunk, but
are you saying we will rework this or we will not ? making it private does not
provide a clear picture.
* Are you concerned that someone might use this accidentally ? What evil are
we trying to prevent by making this private ?
> Reduce the visibility of {{FileSystem#newFSDataOutputStreamBuilder}} before
> the API becomes stable
> --------------------------------------------------------------------------------------------------
>
> Key: HADOOP-14384
> URL: https://issues.apache.org/jira/browse/HADOOP-14384
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs
> Affects Versions: 2.9.0
> Reporter: Lei (Eddy) Xu
> Assignee: Lei (Eddy) Xu
> Priority: Minor
> Attachments: HADOOP-14384.00.patch, HADOOP-14384.01.patch
>
>
> Before {{HADOOP-14365}} finishes, we should limit the this API within Hadoop
> project to prevent it being used by end users or other projects.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
