Thanks Stack, Josh and Andrew for your suggestions and concerns.
I share Stack's suggestions. This would be similar to hbase-thirdparty. The
new repo could be hbase-hbck/hbase-hbck2. As this tool will be used by
hbase users/ developers, hbase JIRA can be used for hbck issues.
bq. How often does
If we do this can we also move out hbck version 1? It would be really weird
in my opinion to have v2 in a separate repo but v1 shipping with the 1.x
releases. That would be a source of understandable confusion.
I believe our compatibility guidelines allow us to upgrade interface
annotations from
I tried backporting the patch to branch-1. There just a few rejects. Would
you be up for creating a backport issue and attaching a version of this
patch that fit branch-1?
Thanks,
S
On Thu, Jul 19, 2018 at 10:12 PM Kang Minwoo
wrote:
> Hello, Users
>
> Our filter is row key filter. So scan time
Thanks, I checked both HBASE-19008 and HBASE-15410, and understood the
reasons why it was changed back to a list from a set.
For now, what I am doing to not bloat up my filterlist is to create sets
which store the row keys so that the duplicates are eliminated, and then
use the set result to
