[
https://issues.apache.org/jira/browse/HDFS-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475098#comment-16475098
]
Chris Douglas commented on HDFS-12615:
--------------------------------------
bq. Right now, this JIRA has become too big, and it has interwoven JIRAs(small
and large) – like you mentioned the Quotas or Multi-subcluster mount points in
the trunk.
Agreed, the number of subtasks for this JIRA belies any coherent theme for
"Phase II" items. The bug fixes, perf improvements, docs, unit tests, and API
cleanup can continue on trunk. As with other modules, they can use tags for
tracking.
bq. I still think at this stage ( perhaps this should have been done much
earlier) that we should open a new branch and revert the changes in trunk and
2.9.
Going through the subtasks, this looks like normal development, just
over-indexed. If a large feature (like security) relies on a web of JIRAs
and/or impacts HDFS significantly, then as you say, that's easier to manage on
a branch.
> 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
