Shout if there is anything you need in it. Meantime help w/ docs, perf,
test, metrics, etc., appreciated.
Thanks.
Your RM,
S
P.S. Current list of 2.0.0 targeted items:
https://issues.apache.org/jira/projects/HBASE/versions/12327188#release-report-tab-body
[
https://issues.apache.org/jira/browse/HBASE-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-20137.
---
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.0.0)
Not on the flakies list anymore, with a
It is just a bit confusing to people who want to attend these events
because it is placed in the agenda section... It looks like that
HBaseCon/PhoenixCon is part of the DataWorks Summit, so maybe some
attendees may want to use the ticket for the DataWorks Summit to enter the
HBaseCon/PhoenixCon?
[
https://issues.apache.org/jira/browse/HBASE-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-20116:
---
> Optimize the region last pushed sequence id layout on zk
>
[
https://issues.apache.org/jira/browse/HBASE-18408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18408.
---
Resolution: Later
Fix Version/s: (was: 2.0.0)
I've not seen this. What is reported here is
On 3/21/18 12:44 PM, Stack wrote:
On Wed, Mar 21, 2018 at 9:26 AM, Josh Elser wrote:
On 3/21/18 2:59 AM, Stack wrote:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
Hi all,
I've published a new website for the upcoming event in June in
+1 (non-binding)
Verified signature and checksum: OK
applied patch in HBASE-20223
Built against branch-2.0, branch-2 and master: OK
ran runSmallTests: NOK all fail on HTTP module but that's most likely
problems with my environment.
started in local mode: OK
ran some shell commands: OK
in the
+1
Checked sums and signatures: ok
RAT check: ok (7u80)
Built from source: ok (7u80)
Unit tests pass: ok (7u80)
1M row LTT: ok (8u152)
250M row ITBLL: ok (8u152)
On Mon, Mar 19, 2018 at 9:48 PM, Francis Liu wrote:
> Hi,
>
> The second release candidate for Apache HBase
stack created HBASE-20248:
-
Summary: [ITBLL] UNREFERENCED rows
Key: HBASE-20248
URL: https://issues.apache.org/jira/browse/HBASE-20248
Project: HBase
Issue Type: Sub-task
Components:
[
https://issues.apache.org/jira/browse/HBASE-20247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-20247.
---
Resolution: Fixed
Assignee: stack
Release Note: Set version as 2.0.0 on branch-2.0.
Pushed to
stack created HBASE-20247:
-
Summary: Set version as 2.0.0 in branch-2.0 in prep for first RC
Key: HBASE-20247
URL: https://issues.apache.org/jira/browse/HBASE-20247
Project: HBase
Issue Type:
On Wed, Mar 21, 2018 at 9:26 AM, Josh Elser wrote:
>
>
> On 3/21/18 2:59 AM, Stack wrote:
>
>> On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
>>
>> Hi all,
>>>
>>> I've published a new website for the upcoming event in June in California
>>> at [1][2]
+1
- signatures checksums: OK
- building from source (8u112): OK
- unit tests: OK
- basic shell commands: OK
- rat test: OK
- LTT with 1M rows (read/write): OK
Just a notice: according to our make_rc.sh script, the sha files should be
named as .sha512.
Thanks,
Balazs
On Wed, Mar 21, 2018 at
Hey Duo,
Thanks for digging into this. I am not surprised by it -- last I talked
to the folks in charge of the website, they mentioned that they would
cross-advertise for us as well. Seems like their web-staff is a bit
faster than I am though. I was planning to point them to our event page
On 3/21/18 2:59 AM, Stack wrote:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are
identical.
I've not yet updated
Odd, it's working for me, Ram.
Let me add both contact emails -- you are right. I had originally
intended to make two websites, but got bogged down in the amount of time
it took to just make one :)
On 3/21/18 2:12 AM, ramkrishna vasudevan wrote:
Hi
I think [2] does not work. Seems to be a
Thanks, Yu! Fixed locally and will push it up shortly.
On 3/21/18 12:12 AM, Yu Li wrote:
Great to know and thanks for the efforts sir.
Minor: in the CfP sector, first line, "The event's call for proposals is
available *on on* EasyChair", the double "on" should be merged (smile)
Best Regards,
[
https://issues.apache.org/jira/browse/HBASE-19552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-19552.
Resolution: Fixed
> update hbase to use new thirdparty libs
>
Chia-Ping Tsai created HBASE-20246:
--
Summary: Remove the spark module
Key: HBASE-20246
URL: https://issues.apache.org/jira/browse/HBASE-20246
Project: HBase
Issue Type: Task
+1 (non-binding)
checked signatures, sums
built from source, ran unit tests
rat check
start from source and bin
basic shell commands
simple operations from basic java client
LTT with 1M rows
Thanks for the release,
Peter
On Tue, Mar 20, 2018 at 5:48 AM, Francis Liu wrote:
>
Balazs Meszaros created HBASE-20245:
---
Summary: HTrace commands do not work
Key: HBASE-20245
URL: https://issues.apache.org/jira/browse/HBASE-20245
Project: HBase
Issue Type: Sub-task
Ted Yu created HBASE-20244:
--
Summary: NoSuchMethodException when retrieving private method
decryptEncryptedDataEncryptionKey from DFSClient
Key: HBASE-20244
URL: https://issues.apache.org/jira/browse/HBASE-20244
Guangxu Cheng created HBASE-20243:
-
Summary: [Shell] Add shell command to create a new table by
cloning the existent table
Key: HBASE-20243
URL: https://issues.apache.org/jira/browse/HBASE-20243
Duo Zhang created HBASE-20242:
-
Summary: The open sequence number will grow if we fail to open a
region after writing the max sequence id file
Key: HBASE-20242
URL: https://issues.apache.org/jira/browse/HBASE-20242
Peter Somogyi created HBASE-20241:
-
Summary: splitormerge_enabled does not work
Key: HBASE-20241
URL: https://issues.apache.org/jira/browse/HBASE-20241
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-20155.
Resolution: Fixed
> update branch-2 version to 2.1.0-SNAPSHOT
>
[
https://issues.apache.org/jira/browse/HBASE-19552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reopened HBASE-19552:
reopen since the spark module was added back to branch-2
> update hbase to use new thirdparty
[
https://issues.apache.org/jira/browse/HBASE-20240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Zhidan resolved HBASE-20240.
---
Resolution: Auto Closed
> CLONE - Add Per-Table metrics back
> --
>
Xu Zhidan created HBASE-20240:
-
Summary: CLONE - Add Per-Table metrics back
Key: HBASE-20240
URL: https://issues.apache.org/jira/browse/HBASE-20240
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reopened HBASE-20155:
reopen since the spark module isn't updated
> update branch-2 version to 2.1.0-SNAPSHOT
>
Zheng Hu created HBASE-20239:
Summary: Scheduled chore task to clean up the last pushed sequence
id for the expired regions.
Key: HBASE-20239
URL: https://issues.apache.org/jira/browse/HBASE-20239
https://dataworkssummit.com/san-jose-2018/
Here, in the Agenda section, HBaseCon and PhoenixCon are also included.
Monday, June 18
8:30 AM - 5:00 PM
Pre-event Training
8:30 AM - 5:00 PM
HBaseCon and PhoenixCon
12:00 PM – 7:00 PM
Registration
6:00 PM – 8:00 PM
Meetups
Is this intentional?
Rahul Gaikwad created HBASE-20238:
-
Summary: Commission and tune heterogeneous nodes like More RAM ,
CPU and HDD capacity in existing running cluster for HDFS and Hbase region
server
Key: HBASE-20238
URL:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
> Hi all,
>
> I've published a new website for the upcoming event in June in California
> at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are
> identical.
>
> I've not yet updated any links on either website
Hi
I think [2] does not work. Seems to be a broken link.
In the CONTACTs section should it be both dev@hbase and dev@phoenix? Rest
looks good to me.
Regards
Ram
On Wed, Mar 21, 2018 at 9:42 AM, Yu Li wrote:
> Great to know and thanks for the efforts sir.
>
> Minor: in the
36 matches
Mail list logo