[jira] [Updated] (HIVE-3291) fix fs resolvers
[ https://issues.apache.org/jira/browse/HIVE-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3291: --- Attachment: HIVE-3291.patch1 fs resolver has hardcoded group id. It should be based on regular expression matching. > fix fs resolvers > - > > Key: HIVE-3291 > URL: https://issues.apache.org/jira/browse/HIVE-3291 > Project: Hive > Issue Type: Bug >Affects Versions: 0.9.0 >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Attachments: HIVE-3291.patch, HIVE-3291.patch1 > > > shims module fails to compile when compiling hive against 1.0 using the fs > resolvers as the force=true flag forces it to use the available version of > hadoop. > In a scenario where you want to build hadoop-1.0 and shims would still want > to build against 20.2 and if you happen to use fs resolver ie > -Dresolvers=true , fs resolvers would just use 1.0 of hadoop for shims and > shims compilation will fail. -- 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] [Updated] (HIVE-3291) fix fs resolvers
[ https://issues.apache.org/jira/browse/HIVE-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3291: --- Affects Version/s: 0.9.0 Status: Patch Available (was: Open) > fix fs resolvers > - > > Key: HIVE-3291 > URL: https://issues.apache.org/jira/browse/HIVE-3291 > Project: Hive > Issue Type: Bug >Affects Versions: 0.9.0 >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Attachments: HIVE-3291.patch, HIVE-3291.patch1 > > > shims module fails to compile when compiling hive against 1.0 using the fs > resolvers as the force=true flag forces it to use the available version of > hadoop. > In a scenario where you want to build hadoop-1.0 and shims would still want > to build against 20.2 and if you happen to use fs resolver ie > -Dresolvers=true , fs resolvers would just use 1.0 of hadoop for shims and > shims compilation will fail. -- 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] [Updated] (HIVE-3291) fix fs resolvers
[ https://issues.apache.org/jira/browse/HIVE-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3291: --- Attachment: HIVE-3291.patch1 > fix fs resolvers > - > > Key: HIVE-3291 > URL: https://issues.apache.org/jira/browse/HIVE-3291 > Project: Hive > Issue Type: Bug >Affects Versions: 0.9.0 >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Attachments: HIVE-3291.patch, HIVE-3291.patch1 > > > shims module fails to compile when compiling hive against 1.0 using the fs > resolvers as the force=true flag forces it to use the available version of > hadoop. > In a scenario where you want to build hadoop-1.0 and shims would still want > to build against 20.2 and if you happen to use fs resolver ie > -Dresolvers=true , fs resolvers would just use 1.0 of hadoop for shims and > shims compilation will fail. -- 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] [Updated] (HIVE-3291) fix fs resolvers
[ https://issues.apache.org/jira/browse/HIVE-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3291: --- Attachment: (was: HIVE-3291.patch1) > fix fs resolvers > - > > Key: HIVE-3291 > URL: https://issues.apache.org/jira/browse/HIVE-3291 > Project: Hive > Issue Type: Bug >Affects Versions: 0.9.0 >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Attachments: HIVE-3291.patch, HIVE-3291.patch1 > > > shims module fails to compile when compiling hive against 1.0 using the fs > resolvers as the force=true flag forces it to use the available version of > hadoop. > In a scenario where you want to build hadoop-1.0 and shims would still want > to build against 20.2 and if you happen to use fs resolver ie > -Dresolvers=true , fs resolvers would just use 1.0 of hadoop for shims and > shims compilation will fail. -- 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] [Updated] (HIVE-3291) fix fs resolvers
[ https://issues.apache.org/jira/browse/HIVE-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3291: --- Attachment: HIVE-3291.patch2 Revised patch for fs resolver. > fix fs resolvers > - > > Key: HIVE-3291 > URL: https://issues.apache.org/jira/browse/HIVE-3291 > Project: Hive > Issue Type: Bug >Affects Versions: 0.9.0 >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Attachments: HIVE-3291.patch, HIVE-3291.patch1, HIVE-3291.patch2 > > > shims module fails to compile when compiling hive against 1.0 using the fs > resolvers as the force=true flag forces it to use the available version of > hadoop. > In a scenario where you want to build hadoop-1.0 and shims would still want > to build against 20.2 and if you happen to use fs resolver ie > -Dresolvers=true , fs resolvers would just use 1.0 of hadoop for shims and > shims compilation will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3736) hive unit test case build failure.
Ashish Singh created HIVE-3736: -- Summary: hive unit test case build failure. Key: HIVE-3736 URL: https://issues.apache.org/jira/browse/HIVE-3736 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.10.0 Environment: hive unit test case build failure. Reporter: Ashish Singh Fix For: 0.10.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3736) hive unit test case build failure.
[ https://issues.apache.org/jira/browse/HIVE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3736: --- Description: Hive depend on hbase-test jar. since classifier is not defined in ivysettings.xml, hence hive is downloading hbase-version.jar as hbase-test.jar. This causes the junit test failures. > hive unit test case build failure. > -- > > Key: HIVE-3736 > URL: https://issues.apache.org/jira/browse/HIVE-3736 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 > Environment: hive unit test case build failure. >Reporter: Ashish Singh > Fix For: 0.10.0 > > > Hive depend on hbase-test jar. > since classifier is not defined in ivysettings.xml, hence hive is downloading > hbase-version.jar as hbase-test.jar. > This causes the junit test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3736) hive unit test case build failure.
[ https://issues.apache.org/jira/browse/HIVE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3736: --- Description: Hive depend on hbase-test jar. since classifier is not defined in ivysettings.xml, hence hive is downloading hbase-.jar as hbase-test-.jar. This causes the junit test failures. was: Hive depend on hbase-test jar. since classifier is not defined in ivysettings.xml, hence hive is downloading hbase-version.jar as hbase-test.jar. This causes the junit test failures. > hive unit test case build failure. > -- > > Key: HIVE-3736 > URL: https://issues.apache.org/jira/browse/HIVE-3736 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 > Environment: hive unit test case build failure. >Reporter: Ashish Singh > Fix For: 0.10.0 > > > Hive depend on hbase-test jar. > since classifier is not defined in ivysettings.xml, hence hive is downloading > hbase-.jar as hbase-test-.jar. > This causes the junit test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3736) hive unit test case build failure.
[ https://issues.apache.org/jira/browse/HIVE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh reassigned HIVE-3736: -- Assignee: Ashish Singh > hive unit test case build failure. > -- > > Key: HIVE-3736 > URL: https://issues.apache.org/jira/browse/HIVE-3736 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 > Environment: hive unit test case build failure. >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > > Hive depend on hbase-test jar. > since classifier is not defined in ivysettings.xml, hence hive is downloading > hbase-.jar as hbase-test-.jar. > This causes the junit test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3736) hive unit test case build failure.
[ https://issues.apache.org/jira/browse/HIVE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3736: --- Attachment: HIVE-3736.patch uploading the patch. > hive unit test case build failure. > -- > > Key: HIVE-3736 > URL: https://issues.apache.org/jira/browse/HIVE-3736 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 > Environment: hive unit test case build failure. >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > Attachments: HIVE-3736.patch > > > Hive depend on hbase-test jar. > since classifier is not defined in ivysettings.xml, hence hive is downloading > hbase-.jar as hbase-test-.jar. > This causes the junit test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3792) hive jars are not part of the share lib tar ball in oozie
Ashish Singh created HIVE-3792: -- Summary: hive jars are not part of the share lib tar ball in oozie Key: HIVE-3792 URL: https://issues.apache.org/jira/browse/HIVE-3792 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.10.0 Reporter: Ashish Singh Assignee: Ashish Singh Fix For: 0.10.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3792) hive jars are not part of the share lib tar ball in oozie
[ https://issues.apache.org/jira/browse/HIVE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3792: --- Description: hive-0.10.0 pom file has missing conf and scope mapping for compile configuration. > hive jars are not part of the share lib tar ball in oozie > - > > Key: HIVE-3792 > URL: https://issues.apache.org/jira/browse/HIVE-3792 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > > hive-0.10.0 pom file has missing conf and scope mapping for compile > configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3792) hive jars are not part of the share lib tar ball in oozie
[ https://issues.apache.org/jira/browse/HIVE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3792: --- Attachment: HIVE-3792.patch > hive jars are not part of the share lib tar ball in oozie > - > > Key: HIVE-3792 > URL: https://issues.apache.org/jira/browse/HIVE-3792 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > Attachments: HIVE-3792.patch > > > hive-0.10.0 pom file has missing conf and scope mapping for compile > configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3792) hive jars are not part of the share lib tar ball in oozie
[ https://issues.apache.org/jira/browse/HIVE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3792: --- Status: Patch Available (was: Open) Attaching the patch, that has the mapping of conf to scope for compile configuration. > hive jars are not part of the share lib tar ball in oozie > - > > Key: HIVE-3792 > URL: https://issues.apache.org/jira/browse/HIVE-3792 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > Attachments: HIVE-3792.patch > > > hive-0.10.0 pom file has missing conf and scope mapping for compile > configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3817) Adding the name space for the maven task for the maven-publish target.
Ashish Singh created HIVE-3817: -- Summary: Adding the name space for the maven task for the maven-publish target. Key: HIVE-3817 URL: https://issues.apache.org/jira/browse/HIVE-3817 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.10.0 Reporter: Ashish Singh Assignee: Ashish Singh Fix For: 0.10.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3817) Adding the name space for the maven task for the maven-publish target.
[ https://issues.apache.org/jira/browse/HIVE-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3817: --- Description: maven task for the maven-publish target is missing from the build.xml. This is causing maven deploy issues. > Adding the name space for the maven task for the maven-publish target. > -- > > Key: HIVE-3817 > URL: https://issues.apache.org/jira/browse/HIVE-3817 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > > maven task for the maven-publish target is missing from the build.xml. > This is causing maven deploy issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3817) Adding the name space for the maven task for the maven-publish target.
[ https://issues.apache.org/jira/browse/HIVE-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3817: --- Attachment: HIVE-3817.patch Adding the patch, that works with hive trunk and hive-0.10.0 branch. > Adding the name space for the maven task for the maven-publish target. > -- > > Key: HIVE-3817 > URL: https://issues.apache.org/jira/browse/HIVE-3817 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > Attachments: HIVE-3817.patch > > > maven task for the maven-publish target is missing from the build.xml. > This is causing maven deploy issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3817) Adding the name space for the maven task for the maven-publish target.
[ https://issues.apache.org/jira/browse/HIVE-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singh updated HIVE-3817: --- Status: Patch Available (was: Open) Patch is available for trunk and 0.10.0 branch. > Adding the name space for the maven task for the maven-publish target. > -- > > Key: HIVE-3817 > URL: https://issues.apache.org/jira/browse/HIVE-3817 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.10.0 >Reporter: Ashish Singh >Assignee: Ashish Singh > Fix For: 0.10.0 > > Attachments: HIVE-3817.patch > > > maven task for the maven-publish target is missing from the build.xml. > This is causing maven deploy issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
