[
https://issues.apache.org/jira/browse/HBASE-8217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616990#comment-13616990
]
Jonathan Hsieh commented on HBASE-8217:
---------------------------------------
bq. This has been discussed a couple of times previously. The argument boils
down to: 0.96 was targeted for fall last year, but having the next 0.96 GA will
take another 2-3 months it seems. As in snapshots, and other issues, it depends
on whether people really care about this feature or not.
I feel that the continued effort backporting is detracting from the ability to
get a 0.95 out or a 0.96 out and continues a negative cycle of further delaying
it.
We basically agreed that the decision is done case-by-case. For me the bar for
backporting features to a stable release is much higher than adding a feature
to trunk or early releases (an x.0 or x.1).
In the case of snapshots, I was against backporting but the justification was
that there were multiple plans backport in distros, and that the feature had
major system/integration/fault-injection testing done to it before it was even
considered merging to trunk let alone 0.94.6. We missed a few minor edge
cases, but I believe we caught all the major ones that a user could easily
trigger, and constantly testied for weeks (in a branch) before merging.
bq. We will mark this as experimental as well. But this will allow us to test
it better and get it rock solid.
I really don't like adding more experimental features to a stable release.
Moreover, the caveat on snapshots to 0.94 was that it wasn't going to be ported
unless it was already solid.
bq. These cases are hopefully covered by the patch.
The *hopefully* part concerns me. If we have some evidence that it is robust
in the face of these cases (a script or integration test that others can run
for a while to test stability), then I'm a lot easier. I haven't done much
research into this but I feel the burden should be on the folks wanting to
backport to make it convincing.
> Port online region merge (HBASE-7403) to 0.94
> ---------------------------------------------
>
> Key: HBASE-8217
> URL: https://issues.apache.org/jira/browse/HBASE-8217
> Project: HBase
> Issue Type: New Feature
> Components: master, Region Assignment, regionserver
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.94.7
>
> Attachments: hbase-8217_v2.patch
>
>
> HBASE-7403 added online region merge, and there was some discussion about
> whether we can port this to 0.94.
> In this issue, we can discuss feasibility and decide one what way or the
> other. I actually have a patch on top of backported HBASE-7721.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
