[jira] [Updated] (HBASE-3539) Improve shell help to reflect all possible options
[
https://issues.apache.org/jira/browse/HBASE-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J Chouraria updated HBASE-3539:
-
Attachment: HBASE-3539.r1.diff
I looked over at all commands in ruby/shell/commands/*.rb and found only 'scan'
to lack what you describe. Added in a minor addition to the 'get' output as
well.
Docs carry a reference to HBASE-2470's patch.
Improve shell help to reflect all possible options
--
Key: HBASE-3539
URL: https://issues.apache.org/jira/browse/HBASE-3539
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.90.0
Reporter: Lars George
Priority: Trivial
Fix For: 0.92.0
Attachments: HBASE-3539.r1.diff
The shell is not consistent in its help texts. For example:
{code}
Scan a table; pass table name and optionally a dictionary of scanner
specifications. Scanner specifications may include one or more of
the following: LIMIT, STARTROW, STOPROW, TIMESTAMP, or COLUMNS. If
no columns are specified, all columns will be scanned.
{code}
but in the code you have
{code}
filter = args[FILTER]
startrow = args[STARTROW] || ''
stoprow = args[STOPROW]
timestamp = args[TIMESTAMP]
columns = args[COLUMNS] || args[COLUMN] || get_all_columns
cache = args[CACHE_BLOCKS] || true
versions = args[VERSIONS] || 1
{code}
VERSIONS is missing from the help.
Check all commands and make sure all options are stated and examples given.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-3818) docs adding troubleshooting.xml
docs adding troubleshooting.xml --- Key: HBASE-3818 URL: https://issues.apache.org/jira/browse/HBASE-3818 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: troubleshooting.xml Adding troubleshooting.xml in docs. The prose is a port of JD's troubleshooting writeup into docbook form. I added shell of common errors at bottom plus added log info at top. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3818) docs adding troubleshooting.xml
[ https://issues.apache.org/jira/browse/HBASE-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-3818: - Attachment: troubleshooting.xml docs adding troubleshooting.xml --- Key: HBASE-3818 URL: https://issues.apache.org/jira/browse/HBASE-3818 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: troubleshooting.xml Adding troubleshooting.xml in docs. The prose is a port of JD's troubleshooting writeup into docbook form. I added shell of common errors at bottom plus added log info at top. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3818) docs adding troubleshooting.xml
[ https://issues.apache.org/jira/browse/HBASE-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13024690#comment-13024690 ] Doug Meil commented on HBASE-3818: -- This still needs to have the book.xml import this (like performance.xml) docs adding troubleshooting.xml --- Key: HBASE-3818 URL: https://issues.apache.org/jira/browse/HBASE-3818 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: troubleshooting.xml Adding troubleshooting.xml in docs. The prose is a port of JD's troubleshooting writeup into docbook form. I added shell of common errors at bottom plus added log info at top. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-1502) Remove need for heartbeats in HBase
[ https://issues.apache.org/jira/browse/HBASE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13024693#comment-13024693 ] jirapos...@reviews.apache.org commented on HBASE-1502: -- --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/647/ --- (Updated 2011-04-24 23:44:37.199842) Review request for hbase. Changes --- Brought this up to the tip of TRUNK. Most tests pass. Looking into a distributed split failure. Summary --- This patch does not completely remove heartbeats. It unburdens the heartbeat of control messages; now heartbeat is used to send the master load only (At most recent hackathon we had rough agreement that we'd keep heartbeat to carry load)... if we miss some, no biggie. RPC version changed on HMasterRegionInfo since the regionServerStartup and regionServerReport arguments have changed. We pass a String now instead of HServerAddress so this should help with our DNS issues where the two sides disagree. Removed HMsg. HServerAddress as been sort_of_deprecated. Its in our API so can't remove it easily (its embedded inside HRegionLocation). Otherwise, we don't use it internally anymore. HServerInfo is deprecated. Server meta data is now available in new class ServerName and load lives apart from HSI now. Fixed up regionserver and master startup so they now look the same. New tests Cruft cleanup. This addresses bug hbase-1502. https://issues.apache.org/jira/browse/hbase-1502 Diffs (updated) - src/main/java/org/apache/hadoop/hbase/ClusterStatus.java 26a8bef src/main/java/org/apache/hadoop/hbase/HConstants.java 5701639 src/main/java/org/apache/hadoop/hbase/HMsg.java 87beb00 src/main/java/org/apache/hadoop/hbase/HRegionLocation.java bd353b8 src/main/java/org/apache/hadoop/hbase/HServerAddress.java 7f8a472 src/main/java/org/apache/hadoop/hbase/HServerInfo.java 0b5bd94 src/main/java/org/apache/hadoop/hbase/HServerLoad.java 2372053 src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java 0d696ab src/main/java/org/apache/hadoop/hbase/MasterAddressTracker.java 1da9742 src/main/java/org/apache/hadoop/hbase/Server.java df396fa src/main/java/org/apache/hadoop/hbase/ServerName.java PRE-CREATION src/main/java/org/apache/hadoop/hbase/avro/AvroUtil.java d7a1e67 src/main/java/org/apache/hadoop/hbase/catalog/CatalogTracker.java be31179 src/main/java/org/apache/hadoop/hbase/catalog/MetaEditor.java c2ee031 src/main/java/org/apache/hadoop/hbase/catalog/MetaReader.java 6e22cf5 src/main/java/org/apache/hadoop/hbase/catalog/RootLocationEditor.java aee64c5 src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java afb666a src/main/java/org/apache/hadoop/hbase/client/HConnection.java 2bb4725 src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java c348f7a src/main/java/org/apache/hadoop/hbase/client/HTable.java edacf56 src/main/java/org/apache/hadoop/hbase/client/RetriesExhaustedWithDetailsException.java 6c62024 src/main/java/org/apache/hadoop/hbase/coprocessor/BaseMasterObserver.java 8df6aa4 src/main/java/org/apache/hadoop/hbase/coprocessor/MasterObserver.java d64817f src/main/java/org/apache/hadoop/hbase/executor/EventHandler.java c22e342 src/main/java/org/apache/hadoop/hbase/executor/RegionTransitionData.java a55f9d6 src/main/java/org/apache/hadoop/hbase/io/HbaseObjectWritable.java d8f8463 src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java ec28de4 src/main/java/org/apache/hadoop/hbase/ipc/HMasterRegionInterface.java 25139b3 src/main/java/org/apache/hadoop/hbase/ipc/HRegionInterface.java 663cab5 src/main/java/org/apache/hadoop/hbase/master/ActiveMasterManager.java 66a3345 src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java 58fdb30 src/main/java/org/apache/hadoop/hbase/master/DeadServer.java 05600c4 src/main/java/org/apache/hadoop/hbase/master/HMaster.java 79a48ba src/main/java/org/apache/hadoop/hbase/master/LoadBalancer.java 6c92cbc src/main/java/org/apache/hadoop/hbase/master/MasterCoprocessorHost.java 4bb072e src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java 55e0162 src/main/java/org/apache/hadoop/hbase/master/ServerManager.java 04befe9 src/main/java/org/apache/hadoop/hbase/master/handler/MetaServerShutdownHandler.java eb01a6a src/main/java/org/apache/hadoop/hbase/master/handler/OpenedRegionHandler.java c478ab7 src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java 60662c2 src/main/java/org/apache/hadoop/hbase/master/handler/SplitRegionHandler.java fee0b3d src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java c065702 src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
[jira] [Resolved] (HBASE-3818) docs adding troubleshooting.xml
[ https://issues.apache.org/jira/browse/HBASE-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-3818. -- Resolution: Fixed Fix Version/s: 0.90.3 Hadoop Flags: [Reviewed] Thanks for the nice addition Doug (and J-D). Committed to TRUNK but will push to the site soon. docs adding troubleshooting.xml --- Key: HBASE-3818 URL: https://issues.apache.org/jira/browse/HBASE-3818 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Fix For: 0.90.3 Attachments: troubleshooting.xml Adding troubleshooting.xml in docs. The prose is a port of JD's troubleshooting writeup into docbook form. I added shell of common errors at bottom plus added log info at top. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-2470) Add Scan.setTimeRange() support in Shell
[ https://issues.apache.org/jira/browse/HBASE-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J Chouraria updated HBASE-2470: - Attachment: HBASE-2470.r2.diff Err, I meant TIMERANGE in the earlier comment. New patch, that adds a test (I failed to notice there was a TestShell). Does this look alright? Add Scan.setTimeRange() support in Shell Key: HBASE-2470 URL: https://issues.apache.org/jira/browse/HBASE-2470 Project: HBase Issue Type: Improvement Affects Versions: 0.20.3 Reporter: Lars George Priority: Trivial Labels: noob Attachments: HBASE-2470.r1.diff, HBASE-2470.r2.diff The shell does not support scans by time range. This is trivial, simply add two more optional values MINTIMESTAMP and MAXTIMESTAMP and if both are set call Scan.setTimeRange(minStamp, maxStamp). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
