[jira] [Created] (HBASE-19693) List Schema
Ethan Wang created HBASE-19693: -- Summary: List Schema Key: HBASE-19693 URL: https://issues.apache.org/jira/browse/HBASE-19693 Project: HBase Issue Type: New Feature Reporter: Ethan Wang Similar to list, there should be a command to list all the distinct schemas from all tables visible. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19692) drop_all/ disable_all Allow regex * in schema portion
Ethan Wang created HBASE-19692: -- Summary: drop_all/ disable_all Allow regex * in schema portion Key: HBASE-19692 URL: https://issues.apache.org/jira/browse/HBASE-19692 Project: HBase Issue Type: New Feature Reporter: Ethan Wang drop_all/ disable_all Allow regex * in schema portion Currently disable_all 'a.b*' is allowed. disable_all '*.b*' is not allowed. When user want to disable_all/drop all the tables with a regx pattern that match all schema, "*.*" will be useful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18394) Allowing user to define levels of prefix of Rowkey to be also put into BloomFilter
[ https://issues.apache.org/jira/browse/HBASE-18394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129501#comment-16129501 ] Ethan Wang commented on HBASE-18394: [~ted_yu]For example, for storing naive time series data, my row key looks like: {code:java} Scope.Metric.Timestamp {code} In this case, there are "three levels" of prefix Scope Metric TimeStamp. Rather than S, Sc, Sco, Scop, > Allowing user to define levels of prefix of Rowkey to be also put into > BloomFilter > -- > > Key: HBASE-18394 > URL: https://issues.apache.org/jira/browse/HBASE-18394 > Project: HBase > Issue Type: Improvement >Reporter: Ethan Wang > > For Time Series data, one common use case is get/scan by prefix of a row key. > Such as: > RowKey:Scope.Metric.TimeStamp > Search by: Scope* > In these case bloom filter is not leveraged. However if we store every prefix > of row key into bloomfilter that will be a big over head. Let user to store > only the prefix of certain level will be a good thing to have > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18435) IntegrationTestingUtility in Hbase-IT not backwards compatible
Ethan Wang created HBASE-18435: -- Summary: IntegrationTestingUtility in Hbase-IT not backwards compatible Key: HBASE-18435 URL: https://issues.apache.org/jira/browse/HBASE-18435 Project: HBase Issue Type: Bug Affects Versions: 1.3.1 Environment: Hbase 1.3.1 Java 1.8 Phoenix 4.11.0 Reporter: Ethan Wang Priority: Minor With Hbase 1.3.1, after a fresh mvn build, Hbase-IT break Phoenix 4.11.0 BaseTest.java Error: HBaseTestingUtility can not be converted into IntegrationTestingUtility -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18394) Allowing user to define levels of prefix of Rowkey to be also put into BloomFilter
Ethan Wang created HBASE-18394: -- Summary: Allowing user to define levels of prefix of Rowkey to be also put into BloomFilter Key: HBASE-18394 URL: https://issues.apache.org/jira/browse/HBASE-18394 Project: HBase Issue Type: Improvement Reporter: Ethan Wang For Time Series data, one common use case is get/scan by prefix of a row key. Such as: RowKey:Scope.Metric.TimeStamp Search by: Scope* In these case bloom filter is not leveraged. However if we store every prefix of row key into bloomfilter that will be a big over head. Let user to store only the prefix of certain level will be a good thing to have -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14247) Separate the old WALs into different regionserver directories
[ https://issues.apache.org/jira/browse/HBASE-14247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014560#comment-16014560 ] Ethan Wang commented on HBASE-14247: [~zghaobac] Are you planning working on this change? > Separate the old WALs into different regionserver directories > - > > Key: HBASE-14247 > URL: https://issues.apache.org/jira/browse/HBASE-14247 > Project: HBase > Issue Type: Improvement > Components: wal >Reporter: Liu Shaohui >Assignee: Liu Shaohui >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-14247-v001.diff, HBASE-14247-v002.diff, > HBASE-14247-v003.diff > > > Currently all old WALs of regionservers are achieved into the single > directory of oldWALs. In big clusters, because of long TTL of WAL or disabled > replications, the number of files under oldWALs may reach the > max-directory-items limit of HDFS, which will make the hbase cluster crashed. > {quote} > Caused by: > org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hdfs.protocol.FSLimitException$MaxDirectoryItemsExceededException): > The directory item limit of /hbase/lgprc-xiaomi/.oldlogs is exceeded: > limit=1048576 items=1048576 > {quote} > A simple solution is to separate the old WALs into different directories > according to the server name of the WAL. > Suggestions are welcomed~ Thanks -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-14247) Separate the old WALs into different regionserver directories
[ https://issues.apache.org/jira/browse/HBASE-14247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1600#comment-1600 ] Ethan Wang commented on HBASE-14247: I have a naive idea. Enhancement like this sounds like to me should implemented from HDFS layer, since HDFS should provide storage as a service? > Separate the old WALs into different regionserver directories > - > > Key: HBASE-14247 > URL: https://issues.apache.org/jira/browse/HBASE-14247 > Project: HBase > Issue Type: Improvement > Components: wal >Reporter: Liu Shaohui >Assignee: Liu Shaohui >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-14247-v001.diff, HBASE-14247-v002.diff, > HBASE-14247-v003.diff > > > Currently all old WALs of regionservers are achieved into the single > directory of oldWALs. In big clusters, because of long TTL of WAL or disabled > replications, the number of files under oldWALs may reach the > max-directory-items limit of HDFS, which will make the hbase cluster crashed. > {quote} > Caused by: > org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hdfs.protocol.FSLimitException$MaxDirectoryItemsExceededException): > The directory item limit of /hbase/lgprc-xiaomi/.oldlogs is exceeded: > limit=1048576 items=1048576 > {quote} > A simple solution is to separate the old WALs into different directories > according to the server name of the WAL. > Suggestions are welcomed~ Thanks -- This message was sent by Atlassian JIRA (v6.3.15#6346)