hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-10856) Prep for 1.0
Date Thu, 27 Mar 2014 23:05:15 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950083#comment-13950083
] 

stack edited comment on HBASE-10856 at 3/27/14 11:04 PM:
---------------------------------------------------------

Here is the thread: http://search-hadoop.com/m/33P7E1GL08b

Here are items.  I'll file issues for them:

* Update included libs (e.g. move to log4j2)
* Enable distributed log replay as default (fix bugs)
* Enable hfilev3 as default.
* Ship with default logging level set to INFO and content of the logs still makes sense
* Enable dynamic config and schema by default.
* Maybe make the hconnection output a bit less verbose when ZK isn't live or HBase still coming
up; it does generate a fair amount of log data
* Light pastel purple colour scheme.
* @Deprecated APIs cleaned up. Delete stale methods or remove the annotations.
* Fix interface audience annotations (HBASE-10462).
* Continue on limiting some broad reaching interfaces (HCM, HCI, HTable) See recent HBASE-10479
discussions)
* Promote HTableInterface vs HTable, getting connections from HCM and getting tables there.
* A clearly defined compatibility strategy between patch, minor, and major versions
* Known coprocessor interfaces. For example right now a coprocessor can use everything on
HRegion. We need to distill what's useful into an interface.
* (wishes for ponies and unicorns, probably not going to happen) better ops supports, such
as sample puppet/chef/etc scripts
* HBASE-4047. (Maybe that makes the 1.0 list?)
* Paring down the coprocessor interfaces to only intercept RPC based actions and move everything
else to plugins...  lots of discussion here including ..."I think the best place to start
is by breaking up some of the current APIs, grouping them around behaviors or areas of functionality.
"
* In HRegion ....extract the public interface out into a Interface. (similar to Store and
HStore)
* HBASE-8763 Combine MVCC and SeqId. Currently replication is broken on same version updates
in the following scenarios: when a region move or RS get restarted in the source cluster,
replicated changes may come out of order to the receiving RS. There are other cases we need
to keep the ordering of puts. This JIRA can be used to fix those above issues.
* Replicated Meta Regions for Distributed Region Location Lookup(I haven't cut a JIRA for
it but I've been thinking this for a while)
* "We need a Replication Interface defined"
* HBASE-9206 'namespace permissions'
* c-client


was (Author: stack):
Here is the thread: http://search-hadoop.com/m/33P7E1GL08b

Here are items.  I'll file issues for them:

* Update included libs (e.g. move to log4j2)
* Enable distributed log replay as default (fix bugs)
* Enable hfilev3 as default.
* Ship with default logging level set to INFO and content of the logs still makes sense
* Enable dynamic config and schema by default.
* Maybe make the hconnection output a bit less verbose when ZK isn't live or HBase still coming
up; it does generate a fair amount of log data
* Light pastel purple colour scheme.
* @Deprecated APIs cleaned up. Delete stale methods or remove the annotations.
+ Fix interface audience annotations (HBASE-10462).
+ Continue on limiting some broad reaching interfaces (HCM, HCI, HTable) See recent HBASE-10479
discussions)
+ Promote HTableInterface vs HTable, getting connections from HCM and getting tables there.
+ A clearly defined compatibility strategy between patch, minor, and major versions
+ Known coprocessor interfaces. For example right now a coprocessor can use everything on
HRegion. We need to distill what's useful into an interface.
+ (wishes for ponies and unicorns, probably not going to happen) better ops supports, such
as sample puppet/chef/etc scripts
+ HBASE-4047. (Maybe that makes the 1.0 list?)
+ Paring down the coprocessor interfaces to only intercept RPC based actions and move everything
else to plugins...  lots of discussion here including ..."I think the best place to start
is by breaking up some of the current APIs, grouping them around behaviors or areas of functionality.
"
+ In HRegion ....extract the public interface out into a Interface. (similar to Store and
HStore)
+ HBASE-8763 Combine MVCC and SeqId. Currently replication is broken on same version updates
in the following scenarios: when a region move or RS get restarted in the source cluster,
replicated changes may come out of order to the receiving RS. There are other cases we need
to keep the ordering of puts. This JIRA can be used to fix those above issues.
+ Replicated Meta Regions for Distributed Region Location Lookup(I haven't cut a JIRA for
it but I've been thinking this for a while)
+  "We need a Replication Interface defined"
+ HBASE-9206 'namespace permissions'


> Prep for 1.0
> ------------
>
>                 Key: HBASE-10856
>                 URL: https://issues.apache.org/jira/browse/HBASE-10856
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: stack
>
> Tasks for 1.0 copied here from our '1.0.0' mailing list discussion.  Idea is to file
subtasks off this one.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message