You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hcatalog-commits@incubator.apache.org by "Alan Gates (JIRA)" <ji...@apache.org> on 2011/06/28 22:37:28 UTC

[jira] [Created] (HCATALOG-53) HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat assume Hadoop running in secure mode

HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat  assume Hadoop running in secure mode
---------------------------------------------------------------------------------------------------

                 Key: HCATALOG-53
                 URL: https://issues.apache.org/jira/browse/HCATALOG-53
             Project: HCatalog
          Issue Type: Bug
    Affects Versions: 0.1
            Reporter: Alan Gates
            Assignee: Alan Gates
            Priority: Blocker
             Fix For: 0.1


If any of these are used when HCatalog is attached to a Hadoop cluster running in non-secure mode, they cause an NPE.  This is because they all assume that the security related configuration parameters are non-null.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HCATALOG-53) HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat assume Hadoop running in secure mode

Posted by "Alan Gates (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HCATALOG-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Gates updated HCATALOG-53:
-------------------------------

    Attachment: HCAT-53.patch

This has not yet been sufficiently tested, so it's not ready for inclusion just yet.

> HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat  assume Hadoop running in secure mode
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HCATALOG-53
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-53
>             Project: HCatalog
>          Issue Type: Bug
>    Affects Versions: 0.1
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>            Priority: Blocker
>             Fix For: 0.1
>
>         Attachments: HCAT-53.patch
>
>
> If any of these are used when HCatalog is attached to a Hadoop cluster running in non-secure mode, they cause an NPE.  This is because they all assume that the security related configuration parameters are non-null.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HCATALOG-53) HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat assume Hadoop running in secure mode

Posted by "Ashutosh Chauhan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HCATALOG-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060143#comment-13060143 ] 

Ashutosh Chauhan commented on HCATALOG-53:
------------------------------------------

HiveConf reads hive-site.xml if found on its classpath when it is instantiated, so ideally all of these properties should come from external xml file, instead of setting and resetting them. For 0.1 timeline this patch is fine, but going forward we should get rid of setting any properties in the code and should read from external config xml files. 

> HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat  assume Hadoop running in secure mode
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HCATALOG-53
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-53
>             Project: HCatalog
>          Issue Type: Bug
>    Affects Versions: 0.1
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>            Priority: Blocker
>             Fix For: 0.1
>
>         Attachments: HCAT-53.patch
>
>
> If any of these are used when HCatalog is attached to a Hadoop cluster running in non-secure mode, they cause an NPE.  This is because they all assume that the security related configuration parameters are non-null.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (HCATALOG-53) HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat assume Hadoop running in secure mode

Posted by "Ashutosh Chauhan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HCATALOG-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashutosh Chauhan resolved HCATALOG-53.
--------------------------------------

    Resolution: Cannot Reproduce

I tried reproducing this on hadoop-20.203 and pig and cant. Moreover, all the unit tests run with security turned off so its unlikely to be an issue. Closing as cannot reproduce, please reopen if issue can be reproduced reliably. 

> HCatLoader, HCatStorer, HCatInputFormat, and HCatOutputFormat  assume Hadoop running in secure mode
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HCATALOG-53
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-53
>             Project: HCatalog
>          Issue Type: Bug
>    Affects Versions: 0.1
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>            Priority: Blocker
>             Fix For: 0.1
>
>         Attachments: HCAT-53.patch
>
>
> If any of these are used when HCatalog is attached to a Hadoop cluster running in non-secure mode, they cause an NPE.  This is because they all assume that the security related configuration parameters are non-null.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira