Re: [NOTICE] defunct branch clean up

[Sean Busbey]

HBASE-15006 has now been closed out.

Thanks everyone!

On Mon, Mar 21, 2016 at 1:03 PM, Sean Busbey  wrote:
> I'd like to clean out some of our defunct git branches.
>
> The current list I'm proposing is in JIRA:
>
> https://issues.apache.org/jira/browse/HBASE-15006
>
>
> If you have a branch you're keeping around and haven't touched in some
> time, please take a look and make sure I'm not including it.
>
>
> Similarly, if you know you had a feature branch at some point in the
> distant past and you're not interested in using it any more, please take a
> look and make sure it's listed.
> --
> busbey

[jira] [Resolved] (HBASE-15006) clean up defunct git branches

[Sean Busbey (JIRA)]

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

Sean Busbey resolved HBASE-15006.
-
Resolution: Fixed

Not sure what release version (if any) to put on this.

Cleaned out the branches mentioned above:

{code}
Busbey-MBA:hbase busbey$ git push origin :branch-2 :0.94-test :asf-site :trunk 
:hbase-7290 :hbase-7290v2 :hbase-6721 :hbase-6721-0.98 :hbase-10070 
:instant_schema_alter :admin :hbase-11339 :HBASE-14337 
:0.89-fb-accidentally-wiped-commit-log 
To https://git-wip-us.apache.org/repos/asf/hbase.git
 - [deleted] 0.89-fb-accidentally-wiped-commit-log
 - [deleted] 0.94-test
 - [deleted] HBASE-14337
 - [deleted] admin
 - [deleted] asf-site
 - [deleted] branch-2
 - [deleted] hbase-10070
 - [deleted] hbase-11339
 - [deleted] hbase-6721
 - [deleted] hbase-6721-0.98
 - [deleted] hbase-7290
 - [deleted] hbase-7290v2
 - [deleted] instant_schema_alter
 - [deleted] trunk
{code}

> clean up defunct git branches
> -
>
> Key: HBASE-15006
> URL: https://issues.apache.org/jira/browse/HBASE-15006
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>
> When the ASF ban on branch deletion is lifted, clean up the mistakenly pushed 
> stuff we have sitting in git.
> This issue should track the discussion of which branches should go.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Nick Dimiduk]

This vote passes with 4 binding +1's and no other votes cast.

Thanks to all who took the time to review this RC.

On Wed, Mar 16, 2016 at 10:13 PM, Nick Dimiduk  wrote:

> I'm happy to announce the first release candidate of HBase 1.1.4 (HBase-
> 1.1.4RC0) is available for download at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.4RC0/
>
> Maven artifacts are also available in the staging repository
> https://repository.apache.org/content/repositories/orgapachehbase-1131/
>
> Artifacts are signed with my code signing subkey 0xAD9039071C3489BD,
> available in the Apache keys directory
> https://people.apache.org/keys/committer/ndimiduk.asc
>
> There's also a signed tag for this release at
> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=70a38529e6d9b24d4b0ab9937b86d0623d037c12
>
> The detailed source and binary compatibility report vs 1.1.3 has been
> published for your review, at 
> *http://home.apache.org/~ndimiduk/1.1.3_1.1.4RC0_compat_report.html
> *
>
> HBase 1.1.4 is the fourth 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 over 40 bug fixes since the 1.1.3
> release. Notable correctness fixes
> include HBASE-15100, HBASE-15218, HBASE-15252, HBASE-15198, HBASE-15214, 
> HBASE-15221, HBASE-15322, HBASE-15378,
> and HBASE-15430.
>
> The full list of fixes included in this release is available at
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12333671
>  and in the CHANGES.txt file included in the distribution.
>
> Please try out this candidate and vote +/-1 by 23:59 Pacific time on
> Sunday, 2016-03-20 as to whether we should release these artifacts as HBase
> 1.1.4.
>
> Thanks,
> Nick
>

[jira] [Resolved] (HBASE-15419) Push HBASE-14850 to apache's git.

[Elliott Clark (JIRA)]

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

Elliott Clark resolved HBASE-15419.
---
Resolution: Done

> Push HBASE-14850 to apache's git.
> -
>
> Key: HBASE-15419
> URL: https://issues.apache.org/jira/browse/HBASE-15419
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Elliott Clark
>
> Now that Apache's git isn't locked down it's time to push the code where it 
> should be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (HBASE-15418) Clean up un-used warning in test util

[Elliott Clark (JIRA)]

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

Elliott Clark resolved HBASE-15418.
---
Resolution: Fixed

Thanks for the review stack.

> Clean up un-used warning in test util
> -
>
> Key: HBASE-15418
> URL: https://issues.apache.org/jira/browse/HBASE-15418
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-15418.patch
>
>
> Clean up the test infra a little bit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15535) Appendix F in the HBase Reference Guide has an incorrect link for Trafodion

[Atanu Mishra (JIRA)]

Atanu Mishra created HBASE-15535:


 Summary: Appendix F in the HBase Reference Guide has an incorrect 
link for Trafodion
 Key: HBASE-15535
 URL: https://issues.apache.org/jira/browse/HBASE-15535
 Project: HBase
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.0.0
Reporter: Atanu Mishra
Priority: Blocker


Appendix F in the HBase Reference Guide available here 
(https://hbase.apache.org/book.html#sql) has an incorrect link to the site for 
Trafodion.

The new Trafodion URL is: http://trafodion.incubator.apache.org/






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (HBASE-14854) Read meta location from zk

[Elliott Clark (JIRA)]

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

Elliott Clark resolved HBASE-14854.
---
Resolution: Fixed

> Read meta location from zk
> --
>
> Key: HBASE-14854
> URL: https://issues.apache.org/jira/browse/HBASE-14854
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-14854-v1.patch, HBASE-14854-v2.patch, 
> HBASE-14854-v3.patch, HBASE-14854.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Google Summer Of Code 2016

[Stack]

Thanks Talat... I shoved some comments up in it but looks basically sound.
Thanks for sending it in.
St.Ack

On Fri, Mar 25, 2016 at 11:09 AM, Talat Uyarer  wrote:

> Hi all,
>
> I created my GSoC proposal for Block Encoding and Compression for RPC
> Layer[1]. If you review and share your comments I will be appreciated.
>
> [1]
> https://docs.google.com/document/d/10MEsmGN5UCh6m-de_nhIG5QYnDRTkmwBTLQ0CRmwOMk/edit?usp=sharing
> [2] https://issues.apache.org/jira/browse/HBASE-15530
>
> Thanks
>
> On Tue, Mar 22, 2016 at 6:44 PM, Talat Uyarer  wrote:
> > Hi,
> >
> > I am appreciated to being mentor Stack :) As I know as ASF already
> > participate and you can sign up. [1] last year I was a mentor. I just
> > send an email to private and ment...@community.apache.org. Would you
> > like to check it ?
> >
> > [1]
> https://community.apache.org/gsoc.html#prospective-asf-mentors-read-this
> >
> > 2016-03-22 17:32 GMT-07:00 Enis Söztutar :
> >>>
> >>> I didn't sign up for GSOC Talat. Not sure anyone else did either. Is
> it too
> >>> late for us to participate now?
> >>>
> >>>
> >> ASF participates in GSOC, so HBase automatically can participate AFAIK.
> >>
> >>
> >>> I'd mentor you (it'd be easy-peasy -- smile) but I think I've missed
> the
> >>> mentor signup deadline.
> >>>
> >>
> >> I did not check the deadline, if that is the case, it means this year is
> >> over?
> >>
> >> Your list is pretty good. We can POC with Capt'n proto as well as grpc.
> >>
> >>
> >>>
> >>>
> >>> > BTW I talked with Enis Soztutar. He offered some topics for GSoC.
> These
> >>> > are:
> >>> > - He mentioned The Data blocks are stored as PREFIX, FAST_DIFF, etc.
> >>> > encoding. But these encodings just can use in HFile context. In RPC
> >>> > and WAL we use KeyValueEncoding for Cell Blocks. He told "You can
> >>> > improve them or using HFile encodings in RPC and WAL" ( He didn't say
> >>> > the issue number But I guessed it is HBASE-12883 Support block
> >>> > encoding based on knowing set of column qualifiers up front)
> >>> >
> >>>
> >>> Sounds like a fine project (Someone was just asking about this
> offline...)
> >>>
> >>>
> >>>
> >>> > - HBASE-14379 Replication V2
> >>> > - HBASE-8691 High-Throughput Streaming Scan API
> >>> > - HBASE-3529 Native Solr Indexer for HBase(He just mentioned HBase ->
> >>> > SOLR indexing. I guess it could be this issue.)
> >>> >
> >>> > Could you help me for selecting topics or could you offer another
> issue ?
> >>> >
> >>> >
> >>> All above are good.
> >>>
> >>> Here's a few others made for another context:
> >>>
> >>> + Become Jepsen distributed systems test tool expert: run it against
> HBase
> >>> and HDFS. Analyze results. E.g. see
> >>> https://www.datastax.com/dev/blog/testing-apache-cassandra-with-jepsen
> >>> + Deep dive on hbase Compactions. Own it. Review current options both
> the
> >>> defaults, experimental, and the stale. Build tooling and surface
> metrics
> >>> that give better insight on effectiveness of compaction mechanics and
> >>> policies. Develop tunings and alternate, new policies. For further
> credit,
> >>> develop master-orchestrated compaction algorithm.
> >>> + Reimplement HBase append and increment as write-only with rollup on
> read
> >>> or using CRDTs (
> >>> https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type)
> >>> + Make the HBase Server async/event driven/SEDA moving it off its
> current
> >>> thread-per-request basis
> >>> + UI: build out more pages and tabs on the HBase master exposing more
> of
> >>> our cluster metrics (make the master into a metrics sink). Extra
> points for
> >>> views, histograms, or dashboards that are both informative AND pretty
> (D3,
> >>> etc.). A good benchmark would be subsuming the Hannibal tool
> >>> https://github.com/sentric/hannibal
> >>> + Build an example application on HBase for test and illustration:
> e.g. use
> >>> Jimmy Lin's/The Internet Archive https://github.com/lintool/warcbase
> to
> >>> load common crawl regular webcrawls https://commoncrawl.org/ or, load
> >>> hbase
> >>> with wikipedia, the flickr dataset, or any dataset that appeals. Extra
> >>> credit for documenting steps involved and filing issues where API is
> >>> awkward or hard to follow.
> >>> + Add actionable statistics to hbase internals that capture vitals
> about
> >>> the data being served and that we exploit responding to queries; e.g.
> rough
> >>> sizes of rows, column-families, columns-per-row-per-region, etc. For
> >>> example, if a client has been stepping sequentially through the data,
> the
> >>> stats would allow us recognize this state so we could switch to a
> different
> >>> scan type; one that is optimal to a sequential progression.
> >>> + Review and redo our fundamental merge sort, the basis of our read.
> There
> >>> are a few techniques to try such as a "loser tree merge" (
> >>> http://sandbox.mc.edu/~bennet/cs402/lec/losedex.html) but ideally we'd
> >>> make
> >>> our merge sort block-based rather than Cell-based. Se

[jira] [Created] (HBASE-15534) A client with basic Get and Put functionality

[Vamsi Mohan V S Thattikota (JIRA)]

Vamsi Mohan V S Thattikota created HBASE-15534:
--

 Summary: A client with basic Get and Put functionality
 Key: HBASE-15534
 URL: https://issues.apache.org/jira/browse/HBASE-15534
 Project: HBase
  Issue Type: Sub-task
  Components: Client
Reporter: Vamsi Mohan V S Thattikota
Assignee: Vamsi Mohan V S Thattikota


This is a C++ client with basic Get and Put API functionality implemented. The 
API is implemented to match close to Java API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Google Summer Of Code 2016

[Talat Uyarer]

Hi all,

I created my GSoC proposal for Block Encoding and Compression for RPC
Layer[1]. If you review and share your comments I will be appreciated.

[1] 
https://docs.google.com/document/d/10MEsmGN5UCh6m-de_nhIG5QYnDRTkmwBTLQ0CRmwOMk/edit?usp=sharing
[2] https://issues.apache.org/jira/browse/HBASE-15530

Thanks

On Tue, Mar 22, 2016 at 6:44 PM, Talat Uyarer  wrote:
> Hi,
>
> I am appreciated to being mentor Stack :) As I know as ASF already
> participate and you can sign up. [1] last year I was a mentor. I just
> send an email to private and ment...@community.apache.org. Would you
> like to check it ?
>
> [1] https://community.apache.org/gsoc.html#prospective-asf-mentors-read-this
>
> 2016-03-22 17:32 GMT-07:00 Enis Söztutar :
>>>
>>> I didn't sign up for GSOC Talat. Not sure anyone else did either. Is it too
>>> late for us to participate now?
>>>
>>>
>> ASF participates in GSOC, so HBase automatically can participate AFAIK.
>>
>>
>>> I'd mentor you (it'd be easy-peasy -- smile) but I think I've missed the
>>> mentor signup deadline.
>>>
>>
>> I did not check the deadline, if that is the case, it means this year is
>> over?
>>
>> Your list is pretty good. We can POC with Capt'n proto as well as grpc.
>>
>>
>>>
>>>
>>> > BTW I talked with Enis Soztutar. He offered some topics for GSoC. These
>>> > are:
>>> > - He mentioned The Data blocks are stored as PREFIX, FAST_DIFF, etc.
>>> > encoding. But these encodings just can use in HFile context. In RPC
>>> > and WAL we use KeyValueEncoding for Cell Blocks. He told "You can
>>> > improve them or using HFile encodings in RPC and WAL" ( He didn't say
>>> > the issue number But I guessed it is HBASE-12883 Support block
>>> > encoding based on knowing set of column qualifiers up front)
>>> >
>>>
>>> Sounds like a fine project (Someone was just asking about this offline...)
>>>
>>>
>>>
>>> > - HBASE-14379 Replication V2
>>> > - HBASE-8691 High-Throughput Streaming Scan API
>>> > - HBASE-3529 Native Solr Indexer for HBase(He just mentioned HBase ->
>>> > SOLR indexing. I guess it could be this issue.)
>>> >
>>> > Could you help me for selecting topics or could you offer another issue ?
>>> >
>>> >
>>> All above are good.
>>>
>>> Here's a few others made for another context:
>>>
>>> + Become Jepsen distributed systems test tool expert: run it against HBase
>>> and HDFS. Analyze results. E.g. see
>>> https://www.datastax.com/dev/blog/testing-apache-cassandra-with-jepsen
>>> + Deep dive on hbase Compactions. Own it. Review current options both the
>>> defaults, experimental, and the stale. Build tooling and surface metrics
>>> that give better insight on effectiveness of compaction mechanics and
>>> policies. Develop tunings and alternate, new policies. For further credit,
>>> develop master-orchestrated compaction algorithm.
>>> + Reimplement HBase append and increment as write-only with rollup on read
>>> or using CRDTs (
>>> https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type)
>>> + Make the HBase Server async/event driven/SEDA moving it off its current
>>> thread-per-request basis
>>> + UI: build out more pages and tabs on the HBase master exposing more of
>>> our cluster metrics (make the master into a metrics sink). Extra points for
>>> views, histograms, or dashboards that are both informative AND pretty (D3,
>>> etc.). A good benchmark would be subsuming the Hannibal tool
>>> https://github.com/sentric/hannibal
>>> + Build an example application on HBase for test and illustration: e.g. use
>>> Jimmy Lin's/The Internet Archive https://github.com/lintool/warcbase to
>>> load common crawl regular webcrawls https://commoncrawl.org/ or, load
>>> hbase
>>> with wikipedia, the flickr dataset, or any dataset that appeals. Extra
>>> credit for documenting steps involved and filing issues where API is
>>> awkward or hard to follow.
>>> + Add actionable statistics to hbase internals that capture vitals about
>>> the data being served and that we exploit responding to queries; e.g. rough
>>> sizes of rows, column-families, columns-per-row-per-region, etc. For
>>> example, if a client has been stepping sequentially through the data, the
>>> stats would allow us recognize this state so we could switch to a different
>>> scan type; one that is optimal to a sequential progression.
>>> + Review and redo our fundamental merge sort, the basis of our read. There
>>> are a few techniques to try such as a "loser tree merge" (
>>> http://sandbox.mc.edu/~bennet/cs402/lec/losedex.html) but ideally we'd
>>> make
>>> our merge sort block-based rather than Cell-based. Set yourself up in a rig
>>> and try different Cell formats to get yourself to a cache-friendly Cell
>>> format that maximizes instructions per cycle.
>>> + Our client is heavy-weight and has accumulated lots of logic over time.
>>> E.g. it is hard to set a single timeout for a request because client is
>>> layered each with its own running timeouts. At its core is a mostly-done
>>> async engine. Review, and fi

[jira] [Created] (HBASE-15533) RSGroup related favored nodes enhancements

[Francis Liu (JIRA)]

Francis Liu created HBASE-15533:
---

 Summary: RSGroup related favored nodes enhancements
 Key: HBASE-15533
 URL: https://issues.apache.org/jira/browse/HBASE-15533
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Thiruvel Thirumoolan






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15532) core favored nodes enhancements

[Francis Liu (JIRA)]

Francis Liu created HBASE-15532:
---

 Summary: core favored nodes enhancements
 Key: HBASE-15532
 URL: https://issues.apache.org/jira/browse/HBASE-15532
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Thiruvel Thirumoolan






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15531) Favored Nodes Enhancements

[Francis Liu (JIRA)]

Francis Liu created HBASE-15531:
---

 Summary: Favored Nodes Enhancements
 Key: HBASE-15531
 URL: https://issues.apache.org/jira/browse/HBASE-15531
 Project: HBase
  Issue Type: Umbrella
Reporter: Francis Liu
Assignee: Francis Liu


We been working on enhancing favored nodes at Yahoo!  See draft document. Feel 
free to comment. I'll add more info.

https://docs.google.com/document/d/1948RKX_-kGUNOHjiYFiKPZnmKWybJkahJYsNibVhcCk/edit?usp=sharing

These enhancements have recently started running in production.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15530) Snappy Compression and Data Block Encoding In RPC

[Talat UYARER (JIRA)]

Talat UYARER created HBASE-15530:


 Summary: Snappy Compression and Data Block Encoding In RPC
 Key: HBASE-15530
 URL: https://issues.apache.org/jira/browse/HBASE-15530
 Project: HBase
  Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Talat UYARER
Assignee: stack


Data block encoding attempts to limit duplication of information in keys, I 
will give support the Data Block Encoding for RPC layer. It will reduce data 
transfer size. But It will probably increase CPU cost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Successful: HBase Generate Website

[Apache Jenkins Server]

Build status: Successful

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/178/artifact/website.patch.zip
 | funzip > 11d11d3fcc591227cccf3531b911e46c68774501.patch
  git fetch
  git checkout -b asf-site-11d11d3fcc591227cccf3531b911e46c68774501 
origin/asf-site
  git am 11d11d3fcc591227cccf3531b911e46c68774501.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local 
asf-site-11d11d3fcc591227cccf3531b911e46c68774501 branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-11d11d3fcc591227cccf3531b911e46c68774501:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-11d11d3fcc591227cccf3531b911e46c68774501 branch:

  git checkout asf-site && git branch -d 
asf-site-11d11d3fcc591227cccf3531b911e46c68774501



If failed, see https://builds.apache.org/job/hbase_generate_website/178/console

[jira] [Created] (HBASE-15529) Override needBalance in StochasticLoadBalancer

[Guanghao Zhang (JIRA)]

Guanghao Zhang created HBASE-15529:
--

 Summary: Override needBalance in StochasticLoadBalancer
 Key: HBASE-15529
 URL: https://issues.apache.org/jira/browse/HBASE-15529
 Project: HBase
  Issue Type: Improvement
Reporter: Guanghao Zhang
Priority: Minor


StochasticLoadBalancer includes cost functions to compute the cost of region 
rount, r/w qps, table load, region locality, memstore size, and storefile size. 
Every cost function returns a number between 0 and 1 inclusive and the computed 
costs are scaled by their respective multipliers. The bigger multiplier means 
that the respective cost function have the bigger weight. But needBalance 
decide whether to balance only by region count and doesn't consider r/w qps, 
locality even you config these cost function with bigger multiplier. 
StochasticLoadBalancer should override needBalance and decide whether to 
balance by it's configs of cost function.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15528) Clean up outdated entries in hbase-default.xml

[Junegunn Choi (JIRA)]

Junegunn Choi created HBASE-15528:
-

 Summary: Clean up outdated entries in hbase-default.xml
 Key: HBASE-15528
 URL: https://issues.apache.org/jira/browse/HBASE-15528
 Project: HBase
  Issue Type: Bug
Reporter: Junegunn Choi
Assignee: Junegunn Choi
Priority: Minor


| {{hbase.bucketcache.sizes}}| Should be 
{{hbase.bucketcache.bucket.sizes}} |
| {{hbase.master.catalog.timeout}}   | Removed in HBASE-7578
|
| {{hbase.regionserver.catalog.timeout}} | Removed in HBASE-7578
|
| {{hbase.metrics.exposeOperationTimes}} | Removed in HBASE-6410
|
| {{hbase.metrics.showTableName}}| Removed in HBASE-6410
|
| {{hbase.thrift.htablepool.size.max}}   | HTablePool is no longer used 
|
| {{zookeeper.znode.rootserver}} | Root region no longer exists 
|




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15527) Refactor Compactor related classes

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-15527:
-

 Summary: Refactor Compactor related classes
 Key: HBASE-15527
 URL: https://issues.apache.org/jira/browse/HBASE-15527
 Project: HBase
  Issue Type: Sub-task
Reporter: Duo Zhang


DefaultCompactor and MultiOutputCompactor still have a lot of duplicate code 
now, need refactoring.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)