andy zhou created HBASE-20340:
-
Summary: potential null pointer exception in
org.apache.hadoop.hbase.rest.TableScanResource given empty resource
Key: HBASE-20340
URL: https://issues.apache.org/jira/browse/HBASE-20340
andy zhou created HBASE-20339:
-
Summary: A potential security issue in
org.apache.hadoop.hbase.http.log.LogLevel.java
Key: HBASE-20339
URL: https://issues.apache.org/jira/browse/HBASE-20339
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-16499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-16499:
-
reopening, please add to the 2.0 upgrade section that calls out changes in
default values to note th
Oh right, also branch-1 currently has HBASE-19858. so we might be a
bit from a 1.5 release.
On Tue, Apr 3, 2018 at 7:25 PM, Sean Busbey wrote:
> I dunno. I'd defer to others on the release suitability of branch-1
> code. I look at nightly and all I see is red.
>
>
>
> On Tue, Apr 3, 2018 at 2:27
I dunno. I'd defer to others on the release suitability of branch-1
code. I look at nightly and all I see is red.
On Tue, Apr 3, 2018 at 2:27 PM, Apekshit Sharma wrote:
> +1 on going back to old behavior, i.e. returning values, in branch-1 and
> 2.0 release.
>
> bq. Open question: should we als
[
https://issues.apache.org/jira/browse/HBASE-15227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Rodionov resolved HBASE-15227.
---
Resolution: Fixed
Done.
> HBase Backup Phase 3: Fault tolerance (client/server) supp
The HBase team is happy to announce the immediate availability of Apache
HBase 1.4.3!
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardware. To le
All,
HBase submits a report to the ASF board once a quarter, to inform the board
about project health. This is my second quarterly report as your PMC chair.
I'm sending the report to the user@ and dev@ mailing lists because you are
the project, and for transparency. If you have any questions about
[
https://issues.apache.org/jira/browse/HBASE-20159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob reopened HBASE-20159:
---
> Support using separate ZK quorums for client
>
>
>
[
https://issues.apache.org/jira/browse/HBASE-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-10933:
---
Reopening. No code committed as per [~ashish singhi]. It looks like process got
a little mangled here. Resolve i
Umesh Agashe created HBASE-20338:
Summary: WALProcedureStore#recoverLease() should have fixed sleeps
and/ or exponential backoff for retrying rollWriter()
Key: HBASE-20338
URL: https://issues.apache.org/jira/brows
+1 on going back to old behavior, i.e. returning values, in branch-1 and
2.0 release.
bq. Open question: should we also revert this change in branch-1.4, even though
it means the shell will behave very differently between maintenance
releases?
Earlier, i was inclining towards reverting the behavio
[
https://issues.apache.org/jira/browse/HBASE-10790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-10790.
-
Resolution: Won't Fix
Assignee: (was: Liu Shaohui)
now covered in the section "build a
[
https://issues.apache.org/jira/browse/HBASE-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-20259.
---
Resolution: Fixed
Pushed. Thanks [~psomogyi]
> Doc configs for in-memory-compaction and add detail to in-mem
stack created HBASE-20337:
-
Summary: Update the doc on how to setup shortcircuit reads; its
stale
Key: HBASE-20337
URL: https://issues.apache.org/jira/browse/HBASE-20337
Project: HBase
Issue Type: S
Sean Busbey created HBASE-20336:
---
Summary:
org.apache.hadoop.hbase.spark.IntegrationTestSparkBulkLoad fails
Key: HBASE-20336
URL: https://issues.apache.org/jira/browse/HBASE-20336
Project: HBase
Sean Busbey created HBASE-20335:
---
Summary: nightly jobs no longer contain machine information
Key: HBASE-20335
URL: https://issues.apache.org/jira/browse/HBASE-20335
Project: HBase
Issue Type:
Sean Busbey created HBASE-20334:
---
Summary: add a test that expressly uses both our shaded client and
the one from hadoop 3
Key: HBASE-20334
URL: https://issues.apache.org/jira/browse/HBASE-20334
Project
Sean Busbey created HBASE-20333:
---
Summary: break up shaded client into one with no Hadoop and one
that's standalone
Key: HBASE-20333
URL: https://issues.apache.org/jira/browse/HBASE-20333
Project: HBase
Sean Busbey created HBASE-20332:
---
Summary: shaded mapreduce module shouldn't include hadoop
Key: HBASE-20332
URL: https://issues.apache.org/jira/browse/HBASE-20332
Project: HBase
Issue Type: Su
Sean Busbey created HBASE-20331:
---
Summary: clean up shaded packaging for 2.0
Key: HBASE-20331
URL: https://issues.apache.org/jira/browse/HBASE-20331
Project: HBase
Issue Type: Umbrella
Over in HBASE-15317 ("document release announcement template
") I had proposed a brief description of our project that sought to
update things to avoid talking about other projects.
at the time (a little over two years ago), stack mentioned that he
liked the phrasing and maybe we should use it in
a table listing would be nice, if we end up using different versions
of maven on different release lines. otherwise, I think having a
minimum version in the pom is sufficient beyond making sure we have a
call out about needing maven 3.
What's the downside to keeping our requirement at 3.0.5? do we
Hi folks!
Wanted to bring your attention to HBASE-20276 "[shell] confirm shell
REPL change and document".
tl;dr: there's a change currently in 1.4.{0..3} and 2.0.0-* that makes
us not return values from any shell commands. current consensus is
that this fundamentally breaks the shell and we shoul
[
https://issues.apache.org/jira/browse/HBASE-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi reopened HBASE-20259:
---
Reopening to fix merge conflict on branch-2.0.
> Doc configs for in-memory-compaction and add de
25 matches
Mail list logo
