The problem was in the documentation of the scan command, not the actual command itself. Scan must take in the name of the table, and may optionally take an array of columns or an array of columns and scanner specifications. Scan will not accept only a table name and scanner specifications. The attached patch makes this more clear in the documentation, and gives the user a warning if they use scan with only a table name and scanner specifications.

Izaak Rubin
added a comment - 09/Jul/08 23:06 - edited The problem was in the documentation of the scan command, not the actual command itself. Scan must take in the name of the table, and may optionally take an array of columns or an array of columns and scanner specifications. Scan will not accept only a table name and scanner specifications. The attached patch makes this more clear in the documentation, and gives the user a warning if they use scan with only a table name and scanner specifications.
The tests in bin/HBase.rb and bin/Formatter.rb all passed.