[jira] [Commented] (HBASE-11873) Hbase Version CLI enhancement

2014-09-11 Thread Guo Ruijing (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-11873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14129709#comment-14129709
 ] 

Guo Ruijing commented on HBASE-11873:
-

We may   ' find .|  grep src/main | grep -e \.java -e \.proto   '

1. source code may include hbase-common/hbase-client, hbase-thrift, etc
2. source code may include .proto.


 Hbase Version CLI enhancement
 -

 Key: HBASE-11873
 URL: https://issues.apache.org/jira/browse/HBASE-11873
 Project: HBase
  Issue Type: Improvement
  Components: build
Reporter: Guo Ruijing
Priority: Minor
  Labels: beginner
 Attachments: HBASE-11873-1.patch, HBASE-11873-2.patch, 
 HBASE-11873.patch


 Hbase Version CLI enhancements:
 1) include source code checksum.
 2) change Subversion to Source code repository
 Existing implementation:
 hadoop@localhost p4_wspaces]$ hbase version
 2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: HBase 0.98.1-hadoop2
 2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Subversion ...
 2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Compiled by ...
 Expected implematation:
 hadoop@localhost p4_wspaces]$ hbase version
 2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: HBase 0.98.1-hadoop2
 2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Source code repository 
 ...change Subversion to Source code repository
 2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Compiled by ...
 2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: From source with 
 checksum eb1b9e8d63c302bed1168a7122d70   include source code checksum



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


[jira] [Created] (HBASE-11873) Hbase Version CLI enhancement

2014-09-01 Thread Guo Ruijing (JIRA)
Guo Ruijing created HBASE-11873:
---

 Summary: Hbase Version CLI enhancement
 Key: HBASE-11873
 URL: https://issues.apache.org/jira/browse/HBASE-11873
 Project: HBase
  Issue Type: Improvement
  Components: build
Reporter: Guo Ruijing
Priority: Minor


Hbase Version CLI enhancements:

1) include source code checksum.
2) change Subversion to Source code repository

Existing implementation:

hadoop@localhost p4_wspaces]$ hbase version
2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: HBase 0.98.1-hadoop2
2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Subversion ...
2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Compiled by ...

Expected implematation:

hadoop@localhost p4_wspaces]$ hbase version
2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: HBase 0.98.1-hadoop2
2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Source code repository 
...change Subversion to Source code repository
2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: Compiled by ...
2014-09-01 03:29:40,773 INFO  [main] util.VersionInfo: From source with 
checksum eb1b9e8d63c302bed1168a7122d70   include source code checksum






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


[jira] [Commented] (HBASE-6184) HRegionInfo was null or empty in Meta

2014-08-12 Thread Guo Ruijing (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093922#comment-14093922
 ] 

Guo Ruijing commented on HBASE-6184:


The issue also happened in hadoop-2.0.5_alpha + hbase-0.94.8 as:

java.io.IOException: HRegionInfo was null or empty in Meta for hbase:namespace, 
row=hbase:namespace,,99
at 
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:152)
at 
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1095)
at 
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1155)
at 
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1047)
at 
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1004)
at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:325)
at org.apache.hadoop.hbase.client.HTable.init(HTable.java:191)
at 
org.apache.hadoop.hbase.master.TableNamespaceManager.isTableAvailableAndInitialized(TableNamespaceManager.java:260)
at 
org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:106)
at 
org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:1044)
at 
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:916)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:603)
at java.lang.Thread.run(Thread.java:744)


 HRegionInfo was null or empty in Meta 
 --

 Key: HBASE-6184
 URL: https://issues.apache.org/jira/browse/HBASE-6184
 Project: HBase
  Issue Type: Bug
  Components: Client, io
Affects Versions: 0.94.0
Reporter: jiafeng.zhang
 Attachments: HBASE-6184.patch


 insert data
 hadoop-0.23.2 + hbase-0.94.0
 2012-06-07 13:09:38,573 WARN  
 [org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation] 
 Encountered problems when prefetch META table: 
 java.io.IOException: HRegionInfo was null or empty in Meta for hbase_one_col, 
 row=hbase_one_col,09115303780247449149,99
 at 
 org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:160)
 at 
 org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:48)
 at 
 org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:126)
 at 
 org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:123)
 at 
 org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:359)
 at 
 org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:123)
 at 
 org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:99)
 at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:894)
 at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:948)
 at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:836)
 at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1482)
 at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1367)
 at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:945)
 at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:801)
 at org.apache.hadoop.hbase.client.HTable.put(HTable.java:776)
 at 
 org.apache.hadoop.hbase.client.HTablePool$PooledHTable.put(HTablePool.java:397)
 at com.dinglicom.hbase.HbaseImport.insertData(HbaseImport.java:177)
 at com.dinglicom.hbase.HbaseImport.run(HbaseImport.java:210)
 at java.lang.Thread.run(Thread.java:662)



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


[jira] [Created] (HBASE-11358) export public classpath for hbase

2014-06-16 Thread Guo Ruijing (JIRA)
Guo Ruijing created HBASE-11358:
---

 Summary: export public classpath for hbase
 Key: HBASE-11358
 URL: https://issues.apache.org/jira/browse/HBASE-11358
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Guo Ruijing


existing behavior for hbase classpath

hbase classpath exports all classpath: (example)
1. avro-1.5.3.jar
2. commons-cli-1.2.jar
3. libthrift-0.8.0.jar
4. all hbase jar

Which is potential conflict with hive using another version of 
libthrift-0.9.0.jar.

We may improve hbase classpath to hbase classpath [all | public]. all 
is default option.

1. hbase classpath all will export all classpath as existing implementation.

2. hbase classpath public will export all hbase public classpath for external 
component.



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


[jira] [Commented] (HBASE-11193) hbase web UI show wrong Catalog Table Description

2014-05-16 Thread Guo Ruijing (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999540#comment-13999540
 ] 

Guo Ruijing commented on HBASE-11193:
-

/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.jamon:

%javaTableName tableName = systemTable.getTableName();/%java
tda href=table.jsp?name=% tableName %% tableName %/a/td
%if (frags != null)%
td align=center% frags.get(tableName.getNameAsString()) != null ? 
frags.get(tableName.getNameAsString())
.intValue() + % : n/a %/td
/%if
%javaString description = null;
if (tableName.equals(TableName.META_TABLE_NAME))
{ description = The hbase:meta table holds references to all User Table 
regions; }

else
{ description = The .NAMESPACE. table holds information about namespaces.; }

/%java
td% description %/td

 we should add tableName.equals(TableName.) for ACL


 hbase web UI show wrong Catalog Table Description
 -

 Key: HBASE-11193
 URL: https://issues.apache.org/jira/browse/HBASE-11193
 Project: HBase
  Issue Type: Bug
  Components: UI
Reporter: Guo Ruijing

 On security cluster, check the hbase master web page and look into 'Catalog 
 Tables' on 'Tables' Section, the Description for 'hbase:acl' table is not 
 expected:
 –
 Table Name Description
 *hbase:acl The .NAMESPACE. table holds information about namespaces.*
 hbase:meta The hbase:meta table holds references to all User Table regions
 hbase:namespace The .NAMESPACE. table holds information about namespaces



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


[jira] [Created] (HBASE-11193) hbase web UI show wrong Catalog Table Description

2014-05-16 Thread Guo Ruijing (JIRA)
Guo Ruijing created HBASE-11193:
---

 Summary: hbase web UI show wrong Catalog Table Description
 Key: HBASE-11193
 URL: https://issues.apache.org/jira/browse/HBASE-11193
 Project: HBase
  Issue Type: Bug
  Components: UI
Reporter: Guo Ruijing


On security cluster, check the hbase master web page and look into 'Catalog 
Tables' on 'Tables' Section, the Description for 'hbase:acl' table is not 
expected:
–
Table Name Description
*hbase:acl The .NAMESPACE. table holds information about namespaces.*
hbase:meta The hbase:meta table holds references to all User Table regions
hbase:namespace The .NAMESPACE. table holds information about namespaces



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


[jira] [Commented] (HBASE-10681) Allow Hbase artifacts to deploy to remote repo other than apache

2014-03-13 Thread Guo Ruijing (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-10681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932962#comment-13932962
 ] 

Guo Ruijing commented on HBASE-10681:
-

JIRA is closed since Roman's solution is good

 Allow Hbase artifacts to deploy to remote repo other than apache
 

 Key: HBASE-10681
 URL: https://issues.apache.org/jira/browse/HBASE-10681
 Project: HBase
  Issue Type: Improvement
  Components: build
Reporter: Guo Ruijing

 pom.xml in hbase write as
  distributionManagement
 site
   idhbase.apache.org/id
   nameHBase Website at hbase.apache.org/name
   !-- On why this is the tmp dir and not hbase.apache.org, see

 https://issues.apache.org/jira/browse/HBASE-7593?focusedCommentId=13555866page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13555866
--
   urlfile:///tmp/url
 /site
 We expect pom.xml in hbase like hadoop can be:
  distributionManagement
   repository
   id${distMgmtStagingId}/id
   name${distMgmtStagingName}/name
   url${distMgmtStagingUrl}/url
 /repository
 snapshotRepository
   id${distMgmtSnapshotsId}/id
   name${distMgmtSnapshotsName}/name
   url${distMgmtSnapshotsUrl}/url
 /snapshotRepository
 site
   idhbase.apache.org/id
   nameHBase Website at hbase.apache.org/name
   !-- On why this is the tmp dir and not hbase.apache.org, see

 https://issues.apache.org/jira/browse/HBASE-7593?focusedCommentId=13555866page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13555866
--
   urlfile:///tmp/url
 /site
   /distributionManagement



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


[jira] [Resolved] (HBASE-10681) Allow Hbase artifacts to deploy to remote repo other than apache

2014-03-13 Thread Guo Ruijing (JIRA)

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

Guo Ruijing resolved HBASE-10681.
-

Resolution: Won't Fix

 Allow Hbase artifacts to deploy to remote repo other than apache
 

 Key: HBASE-10681
 URL: https://issues.apache.org/jira/browse/HBASE-10681
 Project: HBase
  Issue Type: Improvement
  Components: build
Reporter: Guo Ruijing

 pom.xml in hbase write as
  distributionManagement
 site
   idhbase.apache.org/id
   nameHBase Website at hbase.apache.org/name
   !-- On why this is the tmp dir and not hbase.apache.org, see

 https://issues.apache.org/jira/browse/HBASE-7593?focusedCommentId=13555866page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13555866
--
   urlfile:///tmp/url
 /site
 We expect pom.xml in hbase like hadoop can be:
  distributionManagement
   repository
   id${distMgmtStagingId}/id
   name${distMgmtStagingName}/name
   url${distMgmtStagingUrl}/url
 /repository
 snapshotRepository
   id${distMgmtSnapshotsId}/id
   name${distMgmtSnapshotsName}/name
   url${distMgmtSnapshotsUrl}/url
 /snapshotRepository
 site
   idhbase.apache.org/id
   nameHBase Website at hbase.apache.org/name
   !-- On why this is the tmp dir and not hbase.apache.org, see

 https://issues.apache.org/jira/browse/HBASE-7593?focusedCommentId=13555866page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13555866
--
   urlfile:///tmp/url
 /site
   /distributionManagement



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


[jira] [Created] (HBASE-10681) Allow Hbase artifacts to deploy to remote repo other than apache

2014-03-05 Thread Guo Ruijing (JIRA)
Guo Ruijing created HBASE-10681:
---

 Summary: Allow Hbase artifacts to deploy to remote repo other than 
apache
 Key: HBASE-10681
 URL: https://issues.apache.org/jira/browse/HBASE-10681
 Project: HBase
  Issue Type: Improvement
  Components: build
Reporter: Guo Ruijing


pom.xml in hbase write as

 distributionManagement
site
  idhbase.apache.org/id
  nameHBase Website at hbase.apache.org/name
  !-- On why this is the tmp dir and not hbase.apache.org, see
   
https://issues.apache.org/jira/browse/HBASE-7593?focusedCommentId=13555866page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13555866
   --
  urlfile:///tmp/url
/site

We expect pom.xml in hbase like hadoop can be:

 distributionManagement
  repository
  id${distMgmtStagingId}/id
  name${distMgmtStagingName}/name
  url${distMgmtStagingUrl}/url
/repository
snapshotRepository
  id${distMgmtSnapshotsId}/id
  name${distMgmtSnapshotsName}/name
  url${distMgmtSnapshotsUrl}/url
/snapshotRepository
site
  idhbase.apache.org/id
  nameHBase Website at hbase.apache.org/name
  !-- On why this is the tmp dir and not hbase.apache.org, see
   
https://issues.apache.org/jira/browse/HBASE-7593?focusedCommentId=13555866page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13555866
   --
  urlfile:///tmp/url
/site
  /distributionManagement




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