Vishal Khandelwal created HBASE-18889:
-
Summary: Different namenodes url but the same location in are
treated differently
Key: HBASE-18889
URL: https://issues.apache.org/jira/browse/HBASE-18889
Pr
ramkrishna.s.vasudevan created HBASE-1:
--
Summary: StealJobQueue should call super() to init the
PriorityBlockingQueue
Key: HBASE-1
URL: https://issues.apache.org/jira/browse/HBASE-1
Vishal Khandelwal created HBASE-18887:
-
Summary: Full backup passed on hdfs root but incremental failed.
Not able to clean full backup
Key: HBASE-18887
URL: https://issues.apache.org/jira/browse/HBASE-18887
Vishal Khandelwal created HBASE-18886:
-
Summary: Backup command onces cancelled not able re-trigger backup
again
Key: HBASE-18886
URL: https://issues.apache.org/jira/browse/HBASE-18886
Project: HB
JIRA is created, and a patch is attached:
https://issues.apache.org/jira/browse/HBASE-18885
Please review and merge, we need this in the future version. Thanks.
2017-09-26 19:00 GMT+08:00 ShaoFeng Shi :
> Here is the pull request:
>
> https://github.com/apache/hbase/pull/60
>
> 2017-09-26 17:16
Shaofeng SHI created HBASE-18885:
Summary: HFileOutputFormat2 hardcodes default FileOutputCommitter
Key: HBASE-18885
URL: https://issues.apache.org/jira/browse/HBASE-18885
Project: HBase
Issu
Appy created HBASE-18884:
Summary: Coprocessor Design Improvements 2 (Follow up of
HBASE-17732)
Key: HBASE-18884
URL: https://issues.apache.org/jira/browse/HBASE-18884
Project: HBase
Issue Type: Bug
I like the direction.
Pieces of this approach have appeared on various JIRAs, perhaps even some I
might have filed, but of course not so well written. The general idea is to
move away user facing design from the Observer interface subtypes carrying
a huge number of hook points, even if default met
Mike Drob created HBASE-18883:
-
Summary: Upgrade to Curator 4.0
Key: HBASE-18883
URL: https://issues.apache.org/jira/browse/HBASE-18883
Project: HBase
Issue Type: Bug
Components: Client
stack created HBASE-18882:
-
Summary: Run MR branch-1 jobs against hbase2 cluster
Key: HBASE-18882
URL: https://issues.apache.org/jira/browse/HBASE-18882
Project: HBase
Issue Type: Task
Comp
stack created HBASE-18881:
-
Summary: [Coprocessor] Example on how best to keep up a secondary
index
Key: HBASE-18881
URL: https://issues.apache.org/jira/browse/HBASE-18881
Project: HBase
Issue Type:
>
>
> On 9/26/17 11:27 AM, Andrew Purtell wrote:
> > It would be a major functional change. Someone might be relying on the
> > table ownership semantic. However, 2.0 would be the next opportunity to
> > introduce a change of this type before 3.0.
> >
> > I don't think we need table owners. It is a
[
https://issues.apache.org/jira/browse/HBASE-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-18762.
Resolution: Fixed
> Canary sink type cast error
> ---
>
>
On 9/26/17 11:27 AM, Andrew Purtell wrote:
It would be a major functional change. Someone might be relying on the
table ownership semantic. However, 2.0 would be the next opportunity to
introduce a change of this type before 3.0.
I don't think we need table owners. It is a shortcut in the perm
It would be a major functional change. Someone might be relying on the
table ownership semantic. However, 2.0 would be the next opportunity to
introduce a change of this type before 3.0.
I don't think we need table owners. It is a shortcut in the permissions
model which is good for usability but b
The table owner is used by AC. Does it break the BC if we remove the owner from
TD? BTW, https://issues.apache.org/jira/browse/HBASE-11996 try to make the
owner carry more fields, such as email and webpage.
On 2017-09-26 12:07, Sean Busbey wrote:
> In HBASE-6188 we deprecated table owners for
The table owner is used by AC, Is BC broken if we remove the table owner? BTW,
https://issues.apache.org/jira/browse/HBASE-11996 try to make the owner carry
more information, such as email and webpage.
On 2017-09-26 12:07, Sean Busbey wrote:
> In HBASE-6188 we deprecated table owners for the 0
Hbase doesn't use pull request.
Can you open a JIRA and attach patch there ?
Thanks
Original message From: ShaoFeng Shi
Date: 9/26/17 4:00 AM (GMT-08:00) To: dev@hbase.apache.org Subject: Re:
HFileOutputFormat2 hardcodes default FileOutputCommitter
Here is the pull request:
[
https://issues.apache.org/jira/browse/HBASE-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-18762:
---
There is a findbugs warning which I believe is introduced by the patch here.
Seem no pre commit check fo
Guangxu Cheng created HBASE-18880:
-
Summary: Failed to start rest server if the value of
hbase.rest.threads.max is too small.
Key: HBASE-18880
URL: https://issues.apache.org/jira/browse/HBASE-18880
Pr
Here is the pull request:
https://github.com/apache/hbase/pull/60
2017-09-26 17:16 GMT+08:00 ShaoFeng Shi :
> Hello gentlemen,
>
> This is Shaofeng Shi from Apache Kylin community, we use HBase as the
> storage engine, and we use MR job to generate HFile before bulk load. We
> received user repo
Hello gentlemen,
This is Shaofeng Shi from Apache Kylin community, we use HBase as the
storage engine, and we use MR job to generate HFile before bulk load. We
received user reporting that, if configured to use S3 as the output
location for HFile, the files were generated in "_temporary" folder an
22 matches
Mail list logo
