You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2015/08/31 20:34:46 UTC

[jira] [Commented] (ACCUMULO-3972) setshelliter command tries to load class

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

Keith Turner commented on ACCUMULO-3972:
----------------------------------------

I looked into this some more and found the following :
  * Class needs to be loaded in the shell inorder execute option describer
  * The option describer code uses the tables config to load a class
  * After the option desciber code runs there is another check to see if the class can load that does not use the tables config

I think this second check is completely unnecessary.   I think a good fix is to remove the 2nd check and refactor the code so that the 1st check is decoupled from the option describer code  (this makes it clear that the code is reuqired even if the option describer code is changed).

> setshelliter command tries to load class
> ----------------------------------------
>
>                 Key: ACCUMULO-3972
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3972
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.3
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.6.4, 1.7.1, 1.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The setshelliter command does not check that a class exists in the correct way.  It should reach out to  a tserver and see if it can load the iterator class.  Instead the command tries to load the class itself.



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