On Wed, Nov 23, 2011 at 1:02 PM, Jesse Yates <jesse.k.ya...@gmail.com> wrote: > Yeah its time for a bit of redesign, but lets not throw the > baby out with the bath water. > +1
> Another idea that has come up is that often times you want to work in the > context of a table, rather than entering it for every command. Accumulo > does this where you pick the table context to work in. Sometimes its really > simple and nice and other times its a pain when you forget to make the > switch. > IIRC, you can pretty easily modify the irb prompt. We could keep up the current context in the prompt. > I was thinking we could have the option to drop into a table context > (switching into a TabledShell?), but still keep around a lot of the current > functionality. This has implications for the current shell paradigm of > "verb, table, row, etc." (as stack put it), which for some of the current > functionality (eg. coprocessors, attributes, possibly some of the security) > feels a bit forced and awkward. > I always wanted to do: hbase> row = get 'table', 'row' .. and then do hbase> for i in row.columns |col| do.... (or whatever the rubyism for doing this kinda loop). Our help needs a going over tooo.. On the alter 'table' METHOD => table.attr... yeah, thats a bit of a disaster. We should have come up w/ something better than that so appreciate bringing up this discussion Jesse. St.Ack
