Zheng Hu created HBASE-20183:
Summary: Don't split the region in hbase:replication to ensure
that multi-mutations in a batch from replication storage to be atomic
Key: HBASE-20183
URL: https://issues.apache.org/jira/b
Zheng Hu created HBASE-20184:
Summary: Introduce a global configuration to decide whether we use
table or zk based replication storage
Key: HBASE-20184
URL: https://issues.apache.org/jira/browse/HBASE-20184
I thought the problem with releasing 2.0 was that there were too many open
features dragging along not coming to finish- AMv2 (biggest one), CP
cleanup, B&R, etc.
If it was not the case, it wouldn't have been 1 year between first alpha
and GA, rather just few months.
That said, i don't mind new b
I've already merged it to branch-2...
And for the procedure based replication peer modification, the feature has
been finished, at least no critical TODOs. I will not say it has no bugs
but I do not think it will block the 2.1 or 3.0 release too much.
And please trust my judgement, I'm not a man
exactly what Duo said.
Trying something
On Tue, Mar 13, 2018 at 7:44 AM, 张铎(Duo Zhang)
wrote:
> I think the problem is that, in MasterRpcService.execProcedure, we do not
> know the type of the Procedure so it is not possible for us to require
> different permissions for them.
>
> Please ope
Appy created HBASE-20185:
Summary: Fix ACL check for MasterRpcServices#execProcedure
Key: HBASE-20185
URL: https://issues.apache.org/jira/browse/HBASE-20185
Project: HBase
Issue Type: Bug
https://issues.apache.org/jira/browse/HBASE-20185
On Tue, Mar 13, 2018 at 4:35 PM, Apekshit Sharma wrote:
> exactly what Duo said.
>
> Trying something
>
> On Tue, Mar 13, 2018 at 7:44 AM, 张铎(Duo Zhang)
> wrote:
>
>> I think the problem is that, in MasterRpcService.execProcedure, we do not
Xiang Li created HBASE-20186:
Summary: Improve RSG
Key: HBASE-20186
URL: https://issues.apache.org/jira/browse/HBASE-20186
Project: HBase
Issue Type: Improvement
Reporter: Xiang Li
Peter Somogyi created HBASE-20187:
-
Summary: Shell startup fails with
Key: HBASE-20187
URL: https://issues.apache.org/jira/browse/HBASE-20187
Project: HBase
Issue Type: Bug
Compone
Congratulation Guanghao Zhang ..!!
Thanks & Regards,
Pankaj
HUAWEI TECHNOLOGIES CO.LTD.
Huawei Tecnologies India Pvt. Ltd.
Near EPIP Industrial Area, Kundalahalli Village
Whitefield, Bangalore-560066
www.huawei.com
-
Congratulations Ashish..!!
Thanks & Regards,
Pankaj
HUAWEI TECHNOLOGIES CO.LTD.
Huawei Tecnologies India Pvt. Ltd.
Near EPIP Industrial Area, Kundalahalli Village
Whitefield, Bangalore-560066
www.huawei.com
-
Congratulations Mike..!!
Thanks & Regards,
Pankaj
HUAWEI TECHNOLOGIES CO.LTD.
Huawei Tecnologies India Pvt. Ltd.
Near EPIP Industrial Area, Kundalahalli Village
Whitefield, Bangalore-560066
www.huawei.com
---
Congratulations Zach..!!
Thanks & Regards,
Pankaj
HUAWEI TECHNOLOGIES CO.LTD.
Huawei Tecnologies India Pvt. Ltd.
Near EPIP Industrial Area, Kundalahalli Village
Whitefield, Bangalore-560066
www.huawei.com
---
Hello,
This is Amit Anand from Bloomberg. I am trying to figure out the process to
join the HBase slack channel. Can someone help me with this please?
Thank you!
Amit Anand
I took a look. Its great. Our replication is in bad need of loving. The
patch does a refactor/revamp/fix of an internal facility putting our peer
management up on a Pv2 basis. It also moves forward the long-rumored
distributed procedure project.
Its a big change though. Would have been great to ha
stack created HBASE-20188:
-
Summary: [TESTING] Performance
Key: HBASE-20188
URL: https://issues.apache.org/jira/browse/HBASE-20188
Project: HBase
Issue Type: Umbrella
Components: Performanc
Sakthi created HBASE-20189:
--
Summary: Typo in Required Java Version error message while
building HBase.
Key: HBASE-20189
URL: https://issues.apache.org/jira/browse/HBASE-20189
Project: HBase
Issue
To be clear, I didn't mean for this discussion to be some snark directed
at you or the serial-replication feature, Duo. You just happened to be
the first person who put up a merge-vote like this into branch-2 and it
got me thinking. I was/am not trying to throw shade at you.
Let me spin this o
Yep, I totally understand what the problem is and respect how we got
ourselves here. 20185 is on my list to review today.
Thanks for taking it up, Appy.
On 3/13/18 7:41 AM, Apekshit Sharma wrote:
https://issues.apache.org/jira/browse/HBASE-20185
On Tue, Mar 13, 2018 at 4:35 PM, Apekshit Sharm
[
https://issues.apache.org/jira/browse/HBASE-20104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reopened HBASE-20104:
> Fix infinite loop of RIT when creating table on a rsgroup that has no online
> servers
> ---
[
https://issues.apache.org/jira/browse/HBASE-20104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved HBASE-20104.
Resolution: Fixed
Fix Version/s: (was: 1.4.3)
Reverted from branch-1 and branch-1.4
Xiaolin:
If
[
https://issues.apache.org/jira/browse/HBASE-19786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-19786.
---
Resolution: Invalid
This does not fail anymore. Resolving as Invalid.
> acl table is created by coprocessor
stack created HBASE-20190:
-
Summary: Fix default for MIGRATE_TABLE_STATE_FROM_ZK_KEY
Key: HBASE-20190
URL: https://issues.apache.org/jira/browse/HBASE-20190
Project: HBase
Issue Type: Sub-task
I would be interested to be the RM for 2.1 :)
Stack 于2018年3月14日 周三02:48写道：
> I took a look. Its great. Our replication is in bad need of loving. The
> patch does a refactor/revamp/fix of an internal facility putting our peer
> management up on a Pv2 basis. It also moves forward the long-rumored
>
On Tue, Mar 13, 2018 at 6:30 PM, 张铎(Duo Zhang)
wrote:
> I would be interested to be the RM for 2.1 :)
>
>
I could help.
S
> Stack 于2018年3月14日 周三02:48写道：
>
> > I took a look. Its great. Our replication is in bad need of loving. The
> > patch does a refactor/revamp/fix of an internal facility pu
On Tue, Mar 13, 2018 at 8:44 PM, Stack wrote:
> On Tue, Mar 13, 2018 at 6:30 PM, 张铎(Duo Zhang)
> wrote:
>
>> I would be interested to be the RM for 2.1 :)
>>
>>
> I could help.
>
Or, I meant, good... We need more RMs. I volunteer to help smooth the
experience.
S
S
>
>
>
>> Stack 于2018年3月14日 周
[
https://issues.apache.org/jira/browse/HBASE-20181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Appy resolved HBASE-20181.
--
Resolution: Fixed
> Logging and minor logic improvements in BackupLogCleaner
>
> I think Francis Liu might be wanting to make more releases of 1.3. If so,
and for as long as he wants to do it, we shouldn't mark it EOM obviously.
Thanks! Yes, I'd like to continue cutting releases for 1.3 as long as we
are on it which may be a while.
> As for moving the stable pointer to 1.4,
Duo Zhang created HBASE-20191:
-
Summary: Deal with the cleanup of replication barrier for deleted
table
Key: HBASE-20191
URL: https://issues.apache.org/jira/browse/HBASE-20191
Project: HBase
Iss
Not a fan of allowing users (including table and namespace admins) access
to HBase apis that directly allow them to create new files, etc. There's
potential for misuse spamming the NN, broadening the issue.
My 2 cents.
Francis
On Tue, Mar 13, 2018 at 1:49 PM Josh Elser wrote:
> Yep, I totally
30 matches
Mail list logo
