[
https://issues.apache.org/jira/browse/HBASE-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang resolved HBASE-9374.
Resolution: Won't Fix
Assignee: Jimmy Xiang
Close it as Won't Fix for now since no activity.
Liyin Tang created HBASE-10275:
--
Summary: [89-fb] Guarantee the sequenceID in each Region is
strictly monotonic increasing
Key: HBASE-10275
URL: https://issues.apache.org/jira/browse/HBASE-10275
[
https://issues.apache.org/jira/browse/HBASE-9977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark resolved HBASE-9977.
--
Resolution: Fixed
Fix Version/s: 0.99.0
Hadoop Flags: Reviewed
Thanks for all of
Elliott Clark created HBASE-10276:
-
Summary: Hook hbase-native-client up to Native profile.
Key: HBASE-10276
URL: https://issues.apache.org/jira/browse/HBASE-10276
Project: HBase
Issue Type:
We currently have 4 branches (0.94, 0.96, 0.98, and trunk).
For bug and test fixes, do we really need the release managers to agree to
every single check-in.
Andy
currently wants to stabilize the tests in 0.98 so looking at every
change there makes sense and was specifically requested by him.
I think we should have a volunteer on deck as RM for the next major release
at any given time, and so this person would/should be concerned about the
state of trunk. Good idea.
As for me asking for a soft freeze on 0.98, I thank you for your
indulgence and it will be a thing of the past after the
[
https://issues.apache.org/jira/browse/HBASE-10249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reopened HBASE-10249:
Let's reopen the issue.
Intermittent TestReplicationSyncUpTool failure
Sergey Shelukhin created HBASE-10277:
Summary: refactor AsyncProcess
Key: HBASE-10277
URL: https://issues.apache.org/jira/browse/HBASE-10277
Project: HBase
Issue Type: Improvement
Himanshu Vashishtha created HBASE-10278:
---
Summary: Provide better write predictability
Key: HBASE-10278
URL: https://issues.apache.org/jira/browse/HBASE-10278
Project: HBase
Issue
Lars Hofhansl created HBASE-10279:
-
Summary: TestStore.testDeleteExpiredStoreFiles is flaky
Key: HBASE-10279
URL: https://issues.apache.org/jira/browse/HBASE-10279
Project: HBase
Issue Type:
I think I like the idea of a release manger for trunk but is seems like a
potentially all-consuming task requiring superhuman vigilance.
Would working more on feature branches with invested
devs/commiters/shepards is another way of potentially achieving the goal of
a releasable trunk? This could
bq. getting large features or even moderately sized features into branches
off of trunk
+1
We should embrace the above model.
bq. There are a handful these being worked on
I want to mention the unification of mvcc and sequence Id as one more such
feature.
Cheers
On Fri, Jan 3, 2014 at 5:32
Feng Honghua created HBASE-10280:
Summary: Make inMemoryForceMode of LruBlockCache configurable per
column-family
Key: HBASE-10280
URL: https://issues.apache.org/jira/browse/HBASE-10280
Project:
I think features and changes that can reasonably be committed in one go are
fine to go into trunk directly.
For large features (where temporary changes have to stashed somewhere and folks
want to collaborate while the feature is implemented) a branch seems best.
That might in fact be a good
14 matches
Mail list logo
