[jira] [Comment Edited] (ACCUMULO-2929) Cannot interact with columns containing colon in shell

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561369#comment-14561369 ] 

Christopher Tubbs edited comment on ACCUMULO-2929 at 5/27/15 5:57 PM:
----------------------------------------------------------------------

Alternatively, we can add {{-cf}} and {{-cq}} options to the scan command which is mutually exclusive with {{-c}}.


was (Author: ctubbsii):
Alternatively, we can add {{-cf}} and {{-cq}} options to the scan commend which is mutually exclusive with {{-c}}.

> Cannot interact with columns containing colon in shell
> ------------------------------------------------------
>
>                 Key: ACCUMULO-2929
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2929
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Josh Elser
>            Priority: Trivial
>             Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> For context: see http://stackoverflow.com/questions/24295183/is-there-a-way-to-pass-a-column-family-containing-colons-to-the-shells-scan-com
> For commands that have a {{-c}} option (e.g. InsertCommand, GrepCommand, ScanCommand), there is currently no way to specify a column family that contains a colon as it is interpreted as the delimiter between the column family and column qualifier 'cf\[:cq\]'.
> It would be very simple to support a basic escape '\' character that would allow users to use column families which contain colons in the shell.
> For example, to scan for the Key with a row of {{foo}}, a column family of {{person:information}}, and a column qualifier of {{name}}, I should be able to submit the following in the shell:
> {noformat}
> user@instance> scan -r foo -c person\:information:name
> foo person:information:name [] Josh
> {noformat}



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