Re: join hbase slack

2017-08-12 Thread Peter Li 
Can I please have a slack invitation? Thanks.

On Fri, Aug 11, 2017 at 4:35 AM, clara xiong  wrote:

> Could I get one?
>
> On Tue, Jun 20, 2017 at 9:26 AM, Sean Busbey  wrote:
>
> > invite sent!
> >
> > On Tue, Jun 20, 2017 at 12:17 AM, Karan Mehta 
> > wrote:
> > > I want an invite too.
> > >
> > > Thanks,
> > > Karan
> > > ᐧ
> > >
> > > On Mon, Jun 19, 2017 at 6:31 PM, 刘超  wrote:
> > >
> > >> HI，please send me an invite,I want to join hbase slack,thanks
> >
>

[jira] [Created] (HBASE-18587) Fix Flaky TestFileIOEngine

2017-08-12 Thread Zach York (JIRA) 
Zach York created HBASE-18587:
-

 Summary: Fix Flaky TestFileIOEngine
 Key: HBASE-18587
 URL: https://issues.apache.org/jira/browse/HBASE-18587
 Project: HBase
  Issue Type: Bug
  Components: BucketCache, test
Reporter: Zach York
Assignee: Zach York


As a part of HBASE-18533, the Jenkins report said that TestFileIOEngine failed. 
I investigated and noticed that there are two cases where this test is flaky:
len = 0 and offset 0; it will fail for 
https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/bucket/FileIOEngine.java#L198
 will pass in -1 for offset which is invalid.
len = 0 and i = 13; it will try to specify an offset of the totalCapacity which 
is not allowed.
 
This patch fixes this test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18586) Multiple column families - scan performance

2017-08-12 Thread Partha Sarathy (JIRA) 
Partha Sarathy created HBASE-18586:
--

 Summary: Multiple column families - scan performance
 Key: HBASE-18586
 URL: https://issues.apache.org/jira/browse/HBASE-18586
 Project: HBase
  Issue Type: Bug
  Components: scan
Reporter: Partha Sarathy


I have 2 HBase tables - one with a single column family, and other has 4 column 
families. Both tables are keyed by same rowkey, and the column families all 
have a single column qualifier each, with a json string as value (each json 
payload is about 10-20K in size). All column families use fast-diff encoding 
and gzip compression.

After loading about 60MM rows to each table, a scan test on (any) single column 
family in the 2nd table takes 4x the time to scan the single column family from 
the 1st table. In both cases, the scanner is bounded by a start and stop key to 
scan 1MM rows. Performance did not change much even after running a major 
compaction on both tables.

Though HBase doc and other tech forums recommend not using more than 1 column 
family per table, nothing I have read so far suggests scan performance will 
linearly degrade based on number of column families. Has anyone else 
experienced this, and is there a simple explanation for this?

To note, the reason second table has 4 column families is even though I only 
scan one column family at a time now, there are requirements to scan multiple 
column families from that table given a set of rowkeys.

Thanks for any insight into the performance question.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18585) Update release instructions involving gpg-agent

2017-08-12 Thread Nick Dimiduk (JIRA) 
Nick Dimiduk created HBASE-18585:


 Summary: Update release instructions involving gpg-agent
 Key: HBASE-18585
 URL: https://issues.apache.org/jira/browse/HBASE-18585
 Project: HBase
  Issue Type: Task
  Components: build, documentation
Reporter: Nick Dimiduk
Priority: Minor


Could be what I ran into is hyper-local, but making a note here none the less. 
For the build of 1.1.12RC0, I stumbled into MGPG-59. Presumably this is because 
of an graded version of {{gpg-agent}}. The release build takes some time, such 
that even if you purse the advice of invoking gpg before starting the build, 
the default config expires before the build finished on my machine. I haven't 
tested this out yet, but a solution appears to look something like

# configure {{gpg-agent}} with a longer value for {{default-cache-ttl}} in 
{{$HOME/.gnupg/gpg-agent.conf}}.
# invoke {{gpg}} such that the agent will cache the passphrase. MGPG-59 
suggests signing some random file.
# run {{./dev-support/make_release.sh}} as normal.

My context:

{noformat}
diocles:~ ndimiduk$ sw_vers
ProductName:Mac OS X
ProductVersion: 10.11.6
BuildVersion:   15G1611
diocles:~ ndimiduk$ gpg-agent --version
gpg-agent (GnuPG) 2.1.23
libgcrypt 1.8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18584) [hbasecon] Assume domain hbasecon.com

2017-08-12 Thread stack (JIRA) 
stack created HBASE-18584:
-

 Summary: [hbasecon] Assume domain hbasecon.com
 Key: HBASE-18584
 URL: https://issues.apache.org/jira/browse/HBASE-18584
 Project: HBase
  Issue Type: Task
Reporter: stack


Cloudera currently hosts and owns hbasecon.com. They would like to transfer 
ownership and hosting if wanted to hbase PMC. This issue is about assuming the 
domain.

Currently hbasecon.com is pointing at the eventbrite used by hbase asia. 
Eventbrite won't let you link into their site after the event has happened; you 
get redirected to the home page. I've asked to have hbasecon.com point back to 
our archive pages at hbase.apache.org/www.hbasecon.com/. Should be done in next 
day or so.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HBASE-18583) [hbasecon] Update the hbasecon archive

2017-08-12 Thread stack (JIRA) 
stack created HBASE-18583:
-

 Summary: [hbasecon] Update the hbasecon archive
 Key: HBASE-18583
 URL: https://issues.apache.org/jira/browse/HBASE-18583
 Project: HBase
  Issue Type: Task
Reporter: stack


The HBase PMC now hosts the hbasecon archive. It is here: 
http://hbase.apache.org/www.hbasecon.com/

The homepage needs an edit to remove the 'hosted by cloudera' but also to fill 
in hbasecon east 2016, hbasecon west 2017, and the recent hbasecon asia 2017.

The slideshare for hbasecon east needs to have video links added. Ditto for 
hbasecon west and hbasecon asia.

TODO: a blog post on apache hbase site that points at the new updated archive. 
There are also some great pictures from hbasecon asia at least that could do w/ 
uploading. 

Links:

https://www.youtube.com/channel/UCy25rIFxWRBokFg-2Cm83BQ/videos?sort=dd_id=0=0
https://www.slideshare.net/search/slideshow?searchfrom=header=hbaseconeast2016
https://www.slideshare.net/search/slideshow?searchfrom=header=hbasecon2017=any=all=en=
Look for Achieving MultiTenancy.mp4
https://www.slideshare.net/search/slideshow?searchfrom=header=hbaseconasia2017=any=all=en=

Marking this as a beginner task since it mostly admin. I keep meaning to just 
do it but never get to it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] First release candidate for HBase 1.1.12 (RC0) is available

2017-08-12 Thread Nick Dimiduk 
On Sat, Aug 12, 2017 at 3:09 PM, Nick Dimiduk  wrote:

> The detailed source and binary compatibility report vs 1.1.9 has been
> published for your review, at https://home.apache.org/~ndimi
> duk/1.1.11_1.1.12RC0_compat_report.html
>

Apologies; that's a report vs. 1.1.11.

Re: [VOTE] First release candidate for HBase 1.1.12 (RC0) is available

2017-08-12 Thread Nick Dimiduk 
+1

- verified tarballs vs public key on people.apache.org.
- extracted bin tgz:
  - inspect structure. look good.
  - with jdk1.8.0_65:
- run LoadTestTool against standalone bin tgz with FAST_DIFF block
encoder and ROWCOL blooms. No issues, logs look good.
- poked around webUI. looks good.
  - load the site, browsed book.
- extracted src tgz:
  - inspect structure. look good.
  - run LoadTestTool against standalone built from src tgz with FAST_DIFF
block encoder and ROWCOL blooms. No issues, logs look good.
  - poked around webUI. looks good.
- ran the hbase-downstreamer project vs. the staged maven repository. tests
pass.

On Sat, Aug 12, 2017 at 3:09 PM, Nick Dimiduk  wrote:

> I'm happy to announce the first release candidate of HBase 1.1.12
> (HBase-1.1.12RC0) is available for download at https://dist.apache.org/rep
> os/dist/dev/hbase/hbase-1.1.12RC0/
>
> Maven artifacts are also available in the staging repository
> https://repository.apache.org/content/repositories/orgapachehbase-1172
>
> Artifacts are signed with my code signing subkey 0xAD9039071C3489BD,
> available in the Apache keys directory https://people.apache.org/keys
> /committer/ndimiduk.asc and in our KEYS file
> http://www-us.apache.org/dist/hbase/KEYS.
>
> There's also a signed tag for this release at
> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=
> 29a930cdcbef2a64b601a110bad72955b3b04afc
>
> The detailed source and binary compatibility report vs 1.1.9 has been
> published for your review, at https://home.apache.org/~ndimi
> duk/1.1.11_1.1.12RC0_compat_report.html
>
> HBase 1.1.12 is the twelfth patch release in the HBase 1.1 line,
> continuing on the theme of bringing a stable, reliable database to the
> Hadoop and NoSQL communities. This release includes nearly 10 bug fixes
> since the 1.1.11 release. Notable correctness fixes include
> HBASE-9393, HBASE-15691, HBASE-18390, HBASE-18330.
>
> The full list of fixes included in this release is available at
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12310753=12340864 and and in the CHANGES.txt file included
> in the distribution.
>
> Please try out this candidate and vote +/-1 by 23:59 Pacific time on
> Saturday, 2017-08-19 as to whether we should release these artifacts as
> HBase 1.1.12.
>
> Thanks,
> Nick
>

[VOTE] First release candidate for HBase 1.1.12 (RC0) is available

2017-08-12 Thread Nick Dimiduk 
I'm happy to announce the first release candidate of HBase 1.1.12
(HBase-1.1.12RC0) is available for download at https://dist.apache.org/
repos/dist/dev/hbase/hbase-1.1.12RC0/

Maven artifacts are also available in the staging repository
https://repository.apache.org/content/repositories/orgapachehbase-1172

Artifacts are signed with my code signing subkey 0xAD9039071C3489BD,
available in the Apache keys directory https://people.apache.org/
keys/committer/ndimiduk.asc and in our KEYS file
http://www-us.apache.org/dist/hbase/KEYS.

There's also a signed tag for this release at https://git-wip-us.apache.org/
repos/asf?p=hbase.git;a=tag;h=29a930cdcbef2a64b601a110bad72955b3b04afc

The detailed source and binary compatibility report vs 1.1.9 has been
published for your review, at https://home.apache.org/~
ndimiduk/1.1.11_1.1.12RC0_compat_report.html

HBase 1.1.12 is the twelfth patch release in the HBase 1.1 line, continuing
on the theme of bringing a stable, reliable database to the Hadoop and
NoSQL communities. This release includes nearly 10 bug fixes since the
1.1.11 release. Notable correctness fixes include HBASE-9393,
HBASE-15691, HBASE-18390,
HBASE-18330.

The full list of fixes included in this release is available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12310753=12340864 and and in the CHANGES.txt file
included in the distribution.

Please try out this candidate and vote +/-1 by 23:59 Pacific time on
Saturday, 2017-08-19 as to whether we should release these artifacts as
HBase 1.1.12.

Thanks,
Nick

[jira] [Created] (HBASE-18582) Correct the docs for Mutation#setCellVisibility

2017-08-12 Thread Chia-Ping Tsai (JIRA) 
Chia-Ping Tsai created HBASE-18582:
--

 Summary: Correct the docs for Mutation#setCellVisibility
 Key: HBASE-18582
 URL: https://issues.apache.org/jira/browse/HBASE-18582
 Project: HBase
  Issue Type: Task
Reporter: Chia-Ping Tsai
Priority: Minor


{code}
  /**
   * Sets the visibility expression associated with cells in this Mutation.
   * It is illegal to set CellVisibility on Delete 
mutation.
   * @param expression
   */
{code}
HBASE-10885 enable Delete to be specified with Cell Visibility, so we should 
remove the comment " It is illegal to set..."



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (HBASE-15042) refactor so that site materials are in the Standard Maven Place

2017-08-12 Thread Nick Dimiduk (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk reopened HBASE-15042:
--

> refactor so that site materials are in the Standard Maven Place
> ---
>
> Key: HBASE-15042
> URL: https://issues.apache.org/jira/browse/HBASE-15042
> Project: HBase
>  Issue Type: Task
>  Components: build, website
>Reporter: Sean Busbey
>Assignee: Jan Hentschel
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-15042.master.001.patch, 
> HBASE-15042.master.002.patch, HBASE-15042.master.002.patch, 
> HBASE-15042.master.003.patch
>
>
> for some reason we currently have our site materials in {{src/main/site}} 
> rather than the maven prescribed {{src/site}}. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)