You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Brahma Reddy Battula (Created) (JIRA)" <ji...@apache.org> on 2012/04/06 16:31:29 UTC

[jira] [Created] (HADOOP-8254) Log message is same for two different conditions in BlockTokenSecretManager#checkAccess()

Log message is same for two different conditions in BlockTokenSecretManager#checkAccess()
-----------------------------------------------------------------------------------------

                 Key: HADOOP-8254
                 URL: https://issues.apache.org/jira/browse/HADOOP-8254
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs
    Affects Versions: 2.0.0
            Reporter: Brahma Reddy Battula
            Priority: Minor
             Fix For: 2.0.0, 3.0.0


{code}
if (!id.getBlockPoolId().equals(block.getBlockPoolId())) {
      throw new InvalidToken("Block token with " + id.toString()
          + " doesn't apply to block " + block);
    }
    if (id.getBlockId() != block.getBlockId()) {
      throw new InvalidToken("Block token with " + id.toString()
          + " doesn't apply to block " + block);
    }
{code}


--
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] (HADOOP-8254) Log message is same for two different conditions in BlockTokenSecretManager#checkAccess()

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

Suresh Srinivas resolved HADOOP-8254.
-------------------------------------

    Resolution: Duplicate

Not sure multiple jiras for every log message is required. Brahma can you please add it into a single jira, when it is fairly trivial. I am folding this in HADOOP-8252
                
> Log message is same for two different conditions in BlockTokenSecretManager#checkAccess()
> -----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8254
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8254
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 2.0.0
>            Reporter: Brahma Reddy Battula
>            Priority: Minor
>             Fix For: 2.0.0, 3.0.0
>
>
> {code}
> if (!id.getBlockPoolId().equals(block.getBlockPoolId())) {
>       throw new InvalidToken("Block token with " + id.toString()
>           + " doesn't apply to block " + block);
>     }
>     if (id.getBlockId() != block.getBlockId()) {
>       throw new InvalidToken("Block token with " + id.toString()
>           + " doesn't apply to block " + block);
>     }
> {code}

--
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