Jianwei Cui created HBASE-15355:
---
Summary: region.jsp can not be found on info server of master
Key: HBASE-15355
URL: https://issues.apache.org/jira/browse/HBASE-15355
Project: HBase
Issue
Ashu Pachauri created HBASE-15354:
-
Summary: We should use ClientExceptionUtils#isSpecialException
consistently for all operations
Key: HBASE-15354
URL: https://issues.apache.org/jira/browse/HBASE-15354
Elliott Clark created HBASE-15353:
-
Summary: Add metric for number of CallQueueTooBigException's
Key: HBASE-15353
URL: https://issues.apache.org/jira/browse/HBASE-15353
Project: HBase
Issue
Nick Dimiduk created HBASE-15352:
Summary: FST BlockEncoder
Key: HBASE-15352
URL: https://issues.apache.org/jira/browse/HBASE-15352
Project: HBase
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/HBASE-15351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-15351.
---
Resolution: Fixed
Assignee: stack
Fix Version/s: 1.1.4
1.2.1
On Fri, Feb 26, 2016 at 12:23 PM, Andrew Purtell
wrote:
> In the meantime those of us running HBase in production would benefit from
> fairly frequent minor releases.
>
+1. Having to look back to 0.98 to get some new feature is problematic.
On Fri, Feb 26, 2016 at 9:50 AM,
stack created HBASE-15351:
-
Summary: Fix description of hbase.bucketcache.size in
hbase-default.xml
Key: HBASE-15351
URL: https://issues.apache.org/jira/browse/HBASE-15351
Project: HBase
Issue
Zhan Zhang created HBASE-15350:
--
Summary: Enable unit test in hbase-spark module
Key: HBASE-15350
URL: https://issues.apache.org/jira/browse/HBASE-15350
Project: HBase
Issue Type: Sub-task
I think we need at least one success story or one very interested user
with a real project on the line to justify a backport. Otherwise it's a
feature without any users - technically, abandoned.
On Fri, Feb 26, 2016 at 10:11 AM, Ted Yu wrote:
> I am interested in hearing
[
https://issues.apache.org/jira/browse/HBASE-14722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-14722.
---
Resolution: Duplicate
Fix Version/s: (was: 1.3.0)
(was: 2.0.0)
Resolving
There's more in 2.0 than just the assignment manager, too. I think we
should hold off on 2.0 until the pace of change of the offheaping related
work being done on master has slowed and the interface changes have had
some time to bake. It's great work and needs to get out, but is big work
that will
Appy created HBASE-15349:
Summary: Update surefire version to 2.19.1
Key: HBASE-15349
URL: https://issues.apache.org/jira/browse/HBASE-15349
Project: HBase
Issue Type: Improvement
Build status: Successful
If successful, the website and docs have been generated. If failed, skip to the
bottom of this email.
Use the following commands to download the patch and apply it to a clean branch
based on origin/asf-site. If you prefer to keep the hbase-site repo around
I am interested in hearing about user experience with MOB feature as well.
In my opinion, this feature is a nice addition to branch-1.
On Wed, Feb 10, 2016 at 1:45 PM, Andrew Purtell wrote:
> +user@
>
> Is there anyone using the MOB feature in trunk for anything who can
I disagree. We have agreed that 2.0 will have a new assignement manager.
There's a lot of work that has been done on getting that in, so far there
are no benefits to the end user from all that work. We should stick with
the plan and release 2.0 when it's ready.
On Fri, Feb 26, 2016 at 9:39 AM,
Thanks for Mikhail for taking the 1.3 RM role. Looks like we have a lot of
new things in 1.3 release.
Based on the experience of 1.1 and 1.2 release, it takes a lot of efforts
to get a stable minor release out. From this, I have my own 2-cents on 1.4
release. The plan is to have 2.0 release
Elliott Clark created HBASE-15348:
-
Summary: Fix tests broken by recent metrics re-work
Key: HBASE-15348
URL: https://issues.apache.org/jira/browse/HBASE-15348
Project: HBase
Issue Type: Bug
Mikhail Antonov created HBASE-15347:
---
Summary: Update CHANGES.txt for 1.3
Key: HBASE-15347
URL: https://issues.apache.org/jira/browse/HBASE-15347
Project: HBase
Issue Type: Sub-task
Mikhail Antonov created HBASE-15346:
---
Summary: add 1.3 RM to docs
Key: HBASE-15346
URL: https://issues.apache.org/jira/browse/HBASE-15346
Project: HBase
Issue Type: Sub-task
Mikhail Antonov created HBASE-15345:
---
Summary: add branch-1.3 post-commit builds
Key: HBASE-15345
URL: https://issues.apache.org/jira/browse/HBASE-15345
Project: HBase
Issue Type: Sub-task
Mikhail Antonov created HBASE-15344:
---
Summary: add 1.3 to prereq tables in ref guide
Key: HBASE-15344
URL: https://issues.apache.org/jira/browse/HBASE-15344
Project: HBase
Issue Type:
Mikhail Antonov created HBASE-15343:
---
Summary: add branch-1.3 to precommit branches
Key: HBASE-15343
URL: https://issues.apache.org/jira/browse/HBASE-15343
Project: HBase
Issue Type:
Created an umbrella jira for 1.3 release - HBASE-15341
So it looks like we may have 1.4 release before 2.0 is out? I tried to add
1.4 version in jira so we can keep it in branch-1 poms but I couldn't -
looks like I don't have permissions?
-Mikhail
On Thu, Feb 25, 2016 at 3:52 PM, Andrew Purtell
Mikhail Antonov created HBASE-15342:
---
Summary: create branch-1.3
Key: HBASE-15342
URL: https://issues.apache.org/jira/browse/HBASE-15342
Project: HBase
Issue Type: Sub-task
Mikhail Antonov created HBASE-15341:
---
Summary: 1.3 release umbrella
Key: HBASE-15341
URL: https://issues.apache.org/jira/browse/HBASE-15341
Project: HBase
Issue Type: Umbrella
25 matches
Mail list logo