You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Keith Turner (Created) (JIRA)" <ji...@apache.org> on 2012/02/06 19:15:59 UTC

[jira] [Created] (ACCUMULO-372) Deprecate selectrow add row option to scan

Deprecate selectrow add row option to scan
------------------------------------------

                 Key: ACCUMULO-372
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-372
             Project: Accumulo
          Issue Type: Improvement
            Reporter: Keith Turner
             Fix For: 1.4.0


The selectrow command in the shell would not be needed if the scan command had an option to scan a single row.   I propose adding a -r option to scan for scanning over a single row and deprecating the selectrow command.  If this is done in 1.4, we can remove the selectrow command in 1.5.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (ACCUMULO-372) Deprecate selectrow add row option to scan

Posted by "David Medinets (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ACCUMULO-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201847#comment-13201847 ] 

David Medinets commented on ACCUMULO-372:
-----------------------------------------

On the other hand, adding options increases complexity and learning curve. It's easier for someone to scan a list of commands then to scan a list of command and their options. The source code would also be marginally more complex as well?
                
> Deprecate selectrow add row option to scan
> ------------------------------------------
>
>                 Key: ACCUMULO-372
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-372
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.4.0
>
>
> The selectrow command in the shell would not be needed if the scan command had an option to scan a single row.   I propose adding a -r option to scan for scanning over a single row and deprecating the selectrow command.  If this is done in 1.4, we can remove the selectrow command in 1.5.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (ACCUMULO-372) Deprecate selectrow add row option to scan

Posted by "Keith Turner (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Turner resolved ACCUMULO-372.
-----------------------------------

    Resolution: Fixed
      Assignee: Keith Turner
    
> Deprecate selectrow add row option to scan
> ------------------------------------------
>
>                 Key: ACCUMULO-372
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-372
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.4.0
>
>
> The selectrow command in the shell would not be needed if the scan command had an option to scan a single row.   I propose adding a -r option to scan for scanning over a single row and deprecating the selectrow command.  If this is done in 1.4, we can remove the selectrow command in 1.5.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (ACCUMULO-372) Deprecate selectrow add row option to scan

Posted by "Keith Turner (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ACCUMULO-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202522#comment-13202522 ] 

Keith Turner commented on ACCUMULO-372:
---------------------------------------

It seems if you generalize this argument it could really increase the size of the set of commands.  For example we could have the following commands select, selectrow, selectrows, selectrowscolumns, etc.  These commands correspond to different combinations of options for the scan command.  Increasing the size of the set of commands also impacts the learning curve.  Thinking about the list of commands, I opened ACCUMULO-376.  

Having two redundant commands means that both need to be tested and maintained.  ACCUMULO-363 made me think about selectrow, which is redundant and I believe less used than scan (because it has less functionality).  The main issue I worry about w/ deprecating it and removing, is if people are using it in shell scripts.  There is no nice way to deprecate things in the shell like there is in Java. 
                
> Deprecate selectrow add row option to scan
> ------------------------------------------
>
>                 Key: ACCUMULO-372
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-372
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.4.0
>
>
> The selectrow command in the shell would not be needed if the scan command had an option to scan a single row.   I propose adding a -r option to scan for scanning over a single row and deprecating the selectrow command.  If this is done in 1.4, we can remove the selectrow command in 1.5.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira