HBASE-20188 is comparing latest 2.0 to our stable pointer 1.2.7, and there
seems to be no conclusion yet, JFYI. While yes I believe more numbers could
give us a broader view :-)
And I'm not sure but is performance regression some kind of a blocker for
the release? Thanks.
Best Regards,
Yu
On 11
Do we have a ITBLL result and also some performance numbers? I could help
getting some performance numbers comparing to the version we use...
2018-04-11 5:50 GMT+08:00 Sean Busbey :
> no compat report in the RC directory. does that mean we won't have one
> in the dist area?
>
[
https://issues.apache.org/jira/browse/HBASE-20380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-20380.
---
Resolution: Fixed
> Put up 2.0.0RC0
> ---
>
> Key: HBASE-20380
>
stack created HBASE-20385:
-
Summary: Purge md5-making from our little make_rc.sh script
Key: HBASE-20385
URL: https://issues.apache.org/jira/browse/HBASE-20385
Project: HBase
Issue Type: Bug
stack created HBASE-20384:
-
Summary: [AMv2] Logging format improvements; use encoded name
rather than full region name marking transitions
Key: HBASE-20384
URL: https://issues.apache.org/jira/browse/HBASE-20384
stack created HBASE-20383:
-
Summary: [AMv2] AssignmentManager: Failed transition XYZ is not
OPEN
Key: HBASE-20383
URL: https://issues.apache.org/jira/browse/HBASE-20383
Project: HBase
Issue Type:
Mike Drob created HBASE-20382:
-
Summary: If RSGroups not enabled, rsgroup.jsp prints stack trace
Key: HBASE-20382
URL: https://issues.apache.org/jira/browse/HBASE-20382
Project: HBase
Issue
no compat report in the RC directory. does that mean we won't have one
in the dist area?
not a blocker; we've been inconsistent on it in prior releases, but
the trend seemed to be towards including it.
On Tue, Apr 10, 2018 at 3:47 PM, Stack wrote:
> The first release
The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.
Artifacts are available here:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
Maven artifacts are available in the staging repository at:
There are other tools having two versions - o.a.h.h.mapreduce and o.a.h.h.mapred
It seems to me the question is "should hbase support old MR APIs ?' Given that
hadoop 3.0 doesn't mark old MR APIs deprecated, we should keep them in hbase?
Or we can deprecate them in hbase-2+ in order to remove
Sean Busbey created HBASE-20381:
---
Summary: precommit failing w/rat on shadedjars plugin
Key: HBASE-20381
URL: https://issues.apache.org/jira/browse/HBASE-20381
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-20149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-20149.
---
Resolution: Fixed
Assignee: stack (was: Artem Ervits)
Hadoop Flags: Reviewed
Resolving.
>
stack created HBASE-20380:
-
Summary: Put up 2.0.0RC0
Key: HBASE-20380
URL: https://issues.apache.org/jira/browse/HBASE-20380
Project: HBase
Issue Type: Sub-task
Affects Versions: 2.0.0
Sean Busbey created HBASE-20379:
---
Summary: shadedjars yetus plugin should add a footer link
Key: HBASE-20379
URL: https://issues.apache.org/jira/browse/HBASE-20379
Project: HBase
Issue Type:
Hi,
Currently we have 2 RowCounter tools in our
repository: o.a.h.h.mapreduce.RowCounter and o.a.h.h.mapred.RowCounter.
None of them is marked as deprecated but mapred.RowCounter was deprecated
in pre-HBase 1 releases and the annotation was eventually removed
in HBASE-11178.
Do we still want to
Dear,
My name is Stefano, I am a young software developer.
In these months I am using HBase as database in a Hadoop cluster, to write
data from Apache Spark with scala language.
May I ask you any question for specific information?
*Q1*: there is a way to insert/update a specific cell as latest
[
https://issues.apache.org/jira/browse/HBASE-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-20077:
-
> add a project health check that ensures the ref guide can be built
>
[
https://issues.apache.org/jira/browse/HBASE-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-20077.
-
Resolution: Duplicate
> add a project health check that ensures the ref guide can be built
>
[
https://issues.apache.org/jira/browse/HBASE-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-20077.
-
Resolution: Fixed
done by HBASE-15466 you can see the results in current nightly results under
Duo Zhang created HBASE-20378:
-
Summary: Provide a hbck option to cleanup replication barrier for
a table
Key: HBASE-20378
URL: https://issues.apache.org/jira/browse/HBASE-20378
Project: HBase
Duo Zhang created HBASE-20377:
-
Summary: Deal with table in enabling and disabling state when
modifying serial replication peer
Key: HBASE-20377
URL: https://issues.apache.org/jira/browse/HBASE-20377
Peter Somogyi created HBASE-20376:
-
Summary: RowCounter and CellCounter documentations are incorrect
Key: HBASE-20376
URL: https://issues.apache.org/jira/browse/HBASE-20376
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-19843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-19843.
---
Resolution: Duplicate
> Allow temporarily skipping the creation of remote writer for
>
[
https://issues.apache.org/jira/browse/HBASE-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-19080.
---
Resolution: Duplicate
Fix Version/s: (was: 3.0.0)
> Implement a procedure to convert RS
[
https://issues.apache.org/jira/browse/HBASE-19081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-19081.
---
Resolution: Duplicate
Fix Version/s: (was: 3.0.0)
> Implement a procedure to convert RS
25 matches
Mail list logo