Fangyuan Deng created HBASE-18182:
-
Summary: set HBASE_REGIONSERVER_OPTS use UseG1GC will cause
regionserver start error
Key: HBASE-18182
URL: https://issues.apache.org/jira/browse/HBASE-18182
Project
Anoop Sam John created HBASE-18183:
--
Summary: Region interface cleanup for CP expose
Key: HBASE-18183
URL: https://issues.apache.org/jira/browse/HBASE-18183
Project: HBase
Issue Type: Sub-ta
In the 1.2.6 release I'm at the point where I need to update the
website. I've never done this step. I missed it for 1.2.5 and Stack
did the initial publishing sometime between 1.2.4 and 1.2.5.
Last night I started to do it, but fell asleep while reviewing the
changes from essentially taking the d
On 6/7/17 1:17 AM, Stack wrote:
Lets start in on the hardening of hbase-2.0.0. All features are in though
in need of test and polish. There are tasks outstanding around migration
from hbase-1 to hbase-2 and narratives to tell our users around timeout,
etc. We still need to update dependencies,
On Wed, Jun 7, 2017 at 10:04 AM, Josh Elser wrote:
>
>
> On 6/7/17 1:17 AM, Stack wrote:
>>
>
>> I just set the version on master branch to be 3.0.0-SNAPSHOT.
>
>
> I was just thinking about this one this morning: would master become 2.1.0
> or 3.0.0?
>
> I'd guess that the intent is to put more e
On 6/7/17 11:04 AM, Josh Elser wrote:
On 6/7/17 1:17 AM, Stack wrote:
Lets start in on the hardening of hbase-2.0.0. All features are in though
in need of test and polish. There are tasks outstanding around migration
from hbase-1 to hbase-2 and narratives to tell our users around timeout,
etc
On Wed, Jun 7, 2017 at 10:07 AM, Sean Busbey wrote:
> On Wed, Jun 7, 2017 at 10:04 AM, Josh Elser wrote:
>>
>>
>> On 6/7/17 1:17 AM, Stack wrote:
>>>
>>
>>> I just set the version on master branch to be 3.0.0-SNAPSHOT.
>>
>>
>> I was just thinking about this one this morning: would master become
On Wed, Jun 7, 2017 at 10:08 AM, Josh Elser wrote:
>
> On 6/7/17 11:04 AM, Josh Elser wrote:
>>
>>
>>
>> On 6/7/17 1:17 AM, Stack wrote:
>>>
>>> Lets start in on the hardening of hbase-2.0.0. All features are in though
>>> in need of test and polish. There are tasks outstanding around migration
>>
On 6/7/17 11:15 AM, Sean Busbey wrote:
On Wed, Jun 7, 2017 at 10:08 AM, Josh Elser wrote:
On 6/7/17 11:04 AM, Josh Elser wrote:
On 6/7/17 1:17 AM, Stack wrote:
Lets start in on the hardening of hbase-2.0.0. All features are in though
in need of test and polish. There are tasks outstand
On Wed, Jun 7, 2017 at 8:09 AM, Sean Busbey wrote:
I liked Josh's question on where is the hbase-2.0 branch and the reminder
on the Andrew suggestion that we shift release version emphasis left a
digit. Lets try it in hbase-2.
>
> Thinking about this more, did we document the branching strategy
Thanks.
I'd like to see us RM branch-2, branch-1, and master and get away from
narrow focus on the branch-x.y branches that only produce patch releases.
Seems a better use of RM bandwidth to supervise a whole code line.
On Wed, Jun 7, 2017 at 9:52 AM, Stack wrote:
> On Wed, Jun 7, 2017 at 8:09 A
I see no reason why it shouldn't be automated. We can roll back the website
if a broken change is deployed, right?
On Wed, Jun 7, 2017 at 7:27 AM, Sean Busbey wrote:
> In the 1.2.6 release I'm at the point where I need to update the
> website. I've never done this step. I missed it for 1.2.5 and
Alex Araujo created HBASE-18184:
---
Summary: Add hbase-hadoop2-compat jar as MapReduce job dependency
Key: HBASE-18184
URL: https://issues.apache.org/jira/browse/HBASE-18184
Project: HBase
Issue
On Wed, Jun 7, 2017 at 11:13 AM, Andrew Purtell wrote:
> Thanks.
> I'd like to see us RM branch-2, branch-1, and master and get away from
> narrow focus on the branch-x.y branches that only produce patch releases.
> Seems a better use of RM bandwidth to supervise a whole code line.
>
>
I like thi
Balazs Meszaros created HBASE-18185:
---
Summary: IntegrationTestTimeBoundedRequestsWithRegionReplicas
unbalanced tests fails with AssertionError
Key: HBASE-18185
URL: https://issues.apache.org/jira/browse/HBASE-18
Ashu Pachauri created HBASE-18186:
-
Summary: Frequent FileNotFoundExceptions in region server logs
Key: HBASE-18186
URL: https://issues.apache.org/jira/browse/HBASE-18186
Project: HBase
Issue
+1 for 2.0.0-alpha1. It would be really helpful for dependent projects
getting started against the updated apis (e.g. removed deprecated apis).
Jon
On Wed, Jun 7, 2017 at 12:31 PM, Stack wrote:
> On Wed, Jun 7, 2017 at 11:13 AM, Andrew Purtell
> wrote:
>
> > Thanks.
> > I'd like to see us RM
[
https://issues.apache.org/jira/browse/HBASE-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-18184.
Resolution: Fixed
Hadoop Flags: Reviewed
Pushed to master and branch-1. Thanks for th
stack created HBASE-18187:
-
Summary: Release hbase-2.0.0-alpha1
Key: HBASE-18187
URL: https://issues.apache.org/jira/browse/HBASE-18187
Project: HBase
Issue Type: Task
Affects Versions: 2.0.0
On Wed, Jun 7, 2017 at 1:19 PM, Jonathan Hsieh wrote:
> +1 for 2.0.0-alpha1. It would be really helpful for dependent projects
> getting started against the updated apis (e.g. removed deprecated apis).
>
>
Let me push up a rough cut as an RC. Lets see how we do.
St.Ack
> Jon
>
> On Wed, Jun 7
Above plan:
* branch-2 made off of master
* alpha/beta releases tagged off of branch-2
* branch-2.0 made off of branch-2
* 2.0.0 GA release tagged off of branch-2.0
* Follow on minor releases branch-2.y off of branch-2
Looks good. That is what we have done for 1.0/branch-1 as well. The only
thing
Enis Soztutar created HBASE-18188:
-
Summary: [C++] Fix Handling do not retry exceptions
Key: HBASE-18188
URL: https://issues.apache.org/jira/browse/HBASE-18188
Project: HBase
Issue Type: Sub-
On Wed, Jun 7, 2017 at 2:31 PM, Stack wrote:
> On Wed, Jun 7, 2017 at 11:13 AM, Andrew Purtell wrote:
>
>> Thanks.
>> I'd like to see us RM branch-2, branch-1, and master and get away from
>> narrow focus on the branch-x.y branches that only produce patch releases.
>> Seems a better use of RM ban
Sean Busbey created HBASE-18189:
---
Summary: automated job for publishing updated release-specific
docs.
Key: HBASE-18189
URL: https://issues.apache.org/jira/browse/HBASE-18189
Project: HBase
Is
yep, it's just as git as everything else.
filed HBASE-18189 so this doesn't get lost.
On Wed, Jun 7, 2017 at 1:18 PM, Andrew Purtell wrote:
> I see no reason why it shouldn't be automated. We can roll back the website
> if a broken change is deployed, right?
>
> On Wed, Jun 7, 2017 at 7:27 AM, S
stack created HBASE-18190:
-
Summary: Set version in branch-2 to 2.0.0-alpha-1
Key: HBASE-18190
URL: https://issues.apache.org/jira/browse/HBASE-18190
Project: HBase
Issue Type: Sub-task
Affects V
stack created HBASE-18191:
-
Summary: Include hbase-metrics-* in assembly
Key: HBASE-18191
URL: https://issues.apache.org/jira/browse/HBASE-18191
Project: HBase
Issue Type: Sub-task
Report
[
https://issues.apache.org/jira/browse/HBASE-18191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18191.
---
Resolution: Fixed
Assignee: stack
Fix Version/s: 3.0.0
Pushed to branch-2 and master branch.
[
https://issues.apache.org/jira/browse/HBASE-18190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18190.
---
Resolution: Fixed
Pushed to branch-2
> Set version in branch-2 to 2.0.0-alpha-1
> --
The HBase team is happy to announce the immediate availability of Apache
HBase 1.2.6.
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 lea
Ashu Pachauri created HBASE-18192:
-
Summary: Replication drops recovered queues on region server
shutdown
Key: HBASE-18192
URL: https://issues.apache.org/jira/browse/HBASE-18192
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-17876.
-
Resolution: Fixed
> Release 1.2.6
> -
>
> Key: HBASE-17876
>
32 matches
Mail list logo
