[ 
https://issues.apache.org/jira/browse/PIG-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680635#action_12680635
 ] 

Alan Gates commented on PIG-704:
--------------------------------

A comment on the general approach.  I'm wondering if it would be better to tie 
this into the auto-complete functionality in grunt so that it could 
auto-complete alias.

If that isn't feasible, I'm fine with having an aliases keyword to show current 
aliases.  I don't like using '_' to mean something.  Shortcuts should have 
mnemonic value; underscore doesn't mean last alias to me.

> Interactive mode doesn't list defined aliases
> ---------------------------------------------
>
>                 Key: PIG-704
>                 URL: https://issues.apache.org/jira/browse/PIG-704
>             Project: Pig
>          Issue Type: Improvement
>          Components: grunt
>            Reporter: Eric Gaudet
>            Priority: Trivial
>         Attachments: aliases_last.patch
>
>
> I'm using the interactive mode to test my scripts, and I'm struggling to keep 
> track of 2 things:
> 1) the aliases. A typical test script has 10 aliases or more. As the test 
> goes on, different versions are created, or aliases are created with typos. 
> There's no command in grunt to get the list of defined aliases. Proposed 
> solution: add a new command "aliases" that prints the list of aliases.
> 2) I prefer to give meaningful (long) names to my aliases. But as I try 
> different things, I find it hard to predict what the schema will look like, 
> so I use DESCRIBE a lot. It's a pain to type these long names all the time, 
> especially since most of the time I only want to describe the last alias 
> created. A shortcut to the describe command describing the last alias will be 
> very useful. Proposed solution: use the special name "_" as a shortcut to the 
> last created alias: DECRIBE _.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to