[
https://issues.apache.org/jira/browse/HDFS-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477959#comment-16477959
]
Arpit Agarwal commented on HDFS-12615:
--------------------------------------
Hi [~elgoiri], splitting patches sounds like a lot of work. Instead, is it
practical to bring in the large phase 2 changes via a single feature branch
with a design doc (security being an exception)? If that is impractical, can we
have a design or implementation note for each large patch and ensure that
future changes occur in a branch.
A branch also makes it easier to see the impact of a large feature on the
existing code by looking at the merge patch. e.g. proposals like HDFS-13248.
> Router-based HDFS federation phase 2
> ------------------------------------
>
> Key: HDFS-12615
> URL: https://issues.apache.org/jira/browse/HDFS-12615
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Íñigo Goiri
> Assignee: Íñigo Goiri
> Priority: Major
> Labels: RBF
>
> This umbrella JIRA tracks set of improvements over the Router-based HDFS
> federation (HDFS-10467).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
