[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564683#comment-15564683 ] Robert Kanter commented on OOZIE-2613: -- +1 > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch, OOZIE-2613-10.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564554#comment-15564554
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 6 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1815
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3367/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch,
> OOZIE-2613-09.patch, OOZIE-2613-10.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564345#comment-15564345 ] Abhishek Bafna commented on OOZIE-2613: --- Thanks [~rkanter]. Uploading the patch soon. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564339#comment-15564339 ] Robert Kanter commented on OOZIE-2613: -- That seems like a reasonable workaround for now. Can we add a comment to each place explaining why we're setting the user? > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556946#comment-15556946
]
Abhishek Bafna commented on OOZIE-2613:
---
[~rkanter] For three testcase patch uses {{XTestCase#setSystemProperty}} to set
the current user, because with the {{test}} user they are failing with
{{Permission denied}}. Otherwise it is ready. Thanks.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch,
> OOZIE-2613-09.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556597#comment-15556597 ] Robert Kanter commented on OOZIE-2613: -- The latest test-patch run shows all tests green. Is this not ready? > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551869#comment-15551869
]
Abhishek Bafna commented on OOZIE-2613:
---
The directory structure for the partitions are created in the
{{MiniHCatServer#createPartitionDir}} method. I replaced the code with below
but it is still giving the same error.
{code}
public String createPartitionDir(String db, String table, String
partitionSpec, String dbLocation) throws Exception {
FileSystem.get(hadoopConf).mkdirs(new Path(dbLocation),
FsPermission.valueOf("-rwxrwxrwx"));
FileSystem.get(hadoopConf).setOwner(new Path(dbLocation), "test",
"test");
String dir = getPartitionDir(db, table, partitionSpec, dbLocation);
FileSystem.get(hadoopConf).mkdirs(new Path(dir),
FsPermission.valueOf("-rwxrwxrwx"));
FileSystem.get(hadoopConf).setOwner(new Path(dir), "test", "test");
return dir;
}
{code}
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch,
> OOZIE-2613-09.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549726#comment-15549726 ] Rohini Palaniswamy commented on OOZIE-2613: --- bq. The issue was that table/partition get create with the current system user and our testcase was using the 'test' user and they were failing due to permission issue. Most likely has to do with the fact that the directories are created with same permission as the parent. For eg: table directory will be created with same permissions as database directory and partition directory with same permissions as table. HCatStorer for example, does chmod/chgrp during commit phase to ensure that. I assume same is happening here. If you change the owner of the database directory location in the MiniHCatServer.createDatabase() method to the test user then it should work without issues. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537238#comment-15537238
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 6 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1813
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3354/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch,
> OOZIE-2613-09.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536981#comment-15536981 ] Rohini Palaniswamy commented on OOZIE-2613: --- Will take a look later today. Had missed all the earlier questions mentioned with my name. Just found out today that gmail has been filtering most of the "XXX mentioned you" jira emails to the Promotions tab and I have been missing them for more than a year. Sigh :(. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536929#comment-15536929 ] Peter Cseh commented on OOZIE-2613: --- Yaay, I'm glad it fixed the other tests as well :) I'll reach out for some Hive experts on Monday, but they are not familiar with our MiniHCat stuff, so they might not be able to help much. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536918#comment-15536918
]
Abhishek Bafna commented on OOZIE-2613:
---
This fix works for other two testcases as well. The issue was that
table/partition get create with the current system user and our testcase was
using the 'test' user and they were failing due to permission issue.
I agree for the point to do more investigation and fix them properly. If the
lasted patch {{-09}} works, then we can decide whether we want to move ahead
with it or not. Thanks for the feedback.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch,
> OOZIE-2613-09.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536906#comment-15536906 ] Peter Cseh commented on OOZIE-2613: --- I'm not sure setting this is the right way to fix it. If we decide to do it anyway as the problem is with the test, not the actual code, please file a follow up jira to get to the bottom of this testing issue. There are still two more test cases which I haven't had the chance to look at, so this fix might not be sufficient. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, > OOZIE-2613-09.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536857#comment-15536857 ] Abhishek Bafna commented on OOZIE-2613: --- [~rkanter] i.e. a great method, I guess. I will test it and then submit a patch, If it works. :) > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536830#comment-15536830
]
Robert Kanter commented on OOZIE-2613:
--
If you use {{XTestCase#setSystemProperty}} to do it, then Oozie will
automatically take care of that :)
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536818#comment-15536818 ] Abhishek Bafna commented on OOZIE-2613: --- [~gezapeti] If we set this into the system property then it will be set for the rest of the testcase execution, which can cause the other testcases to fail. May be we can reset it to its original value at the end of the test. cc: [~rkanter] > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536790#comment-15536790
]
Peter Cseh commented on OOZIE-2613:
---
It's easier to add the line
{code}System.setProperty(XTestCase.TEST_USER1_PROP, );
{code}
to {{testDeleteHCat}} to test this. This will make the test to delete the table
as your current user and will make the test pass.
[~rkanter], I could not change the user of {{MiniHCatServer}}, but I'm sure
it's possible. I'll look into this more on Monday.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536777#comment-15536777 ] Robert Kanter commented on OOZIE-2613: -- I could be wrong here, but I imagine that in a production environment, the HCat Server would be running as the 'hive' user, and the clients would be running as the actual user. So the HCat Server should allow for doing things as other users, but in our setup, it seems like it does things only as the HCat Server user, which is the OS user. Perhaps we need to look into how HCat Client determines the user and use that to run the client as 'test' and then hopefully the HCat Server will do things on behalf of 'test'? > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536726#comment-15536726
]
Peter Cseh commented on OOZIE-2613:
---
I managed to fix {{TestFsActionExecutor#testDeleteHcat}} by using my OS user
name, {{gezapeti}}, in {{FsActionExecutor#delete}} instead of the user
{{test}}. But this "fix" would actually break things in production.
The problem is with the test:
The table is created by {{MiniHCatServer}} and it's {{gezapeti}} who creates
the table, and user {{test}} don't have the permissions to delete it.
Unfortunately, I could not find a way to make {{MiniHCatServer}} to use the
user {{test}} or give permissions to drop table to that user. Anyone has any
ideas? [~abhishekbafna]?
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15534679#comment-15534679 ] Robert Kanter commented on OOZIE-2613: -- I tried using a proxy user with doAs and that didn't work. But it looks like Falcon is doing something like that, but maybe they're doing something we're missing? Or maybe they're not using a fake "test" user. Anyway, maybe this will have something useful? https://github.com/apache/falcon/blob/master/common/src/main/java/org/apache/falcon/catalog/HiveCatalogService.java#L146 > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15533688#comment-15533688 ] Abhishek Bafna commented on OOZIE-2613: --- [~gezapeti], [~asasvari], [~satishsaley], [~pbacsko], [~puru], [~jaydeepvishwakarma] Any ideas or help would be great to resolve the above testcase with Hive upgrade. Thanks. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532868#comment-15532868
]
Abhishek Bafna commented on OOZIE-2613:
---
There are three testcase which fails with the same Permission error:
Tests:
{noformat}
org.apache.oozie.action.hadoop.TestFsActionExecutor.testDeleteHcat
org.apache.oozie.command.coord.TestCoordRerunXCommand.testCoordRerunCleanupForHCat
org.apache.oozie.dependency.TestHCatURIHandler.testExists
{noformat}
Error:
{code}
org.apache.oozie.BaseEngineException: E0907: Failed to delete uri : E1501:
Error in getting HCat Access [org.apache.hive.hcatalog.common.HCatException :
9001 : Exception occurred while processing HCat request : MetaException while
dropping partition.. Cause : MetaException(message:Got exception:
org.apache.hadoop.security.AccessControlException Permission denied: user=test,
access=WRITE,
inode="/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/core/target/test-data/oozietests/org.apache.oozie.command.coord.TestCoordRerunXCommand/testCoordRerunCleanupForHCat/mydb/mytable/ds=2009121411":jenkins:supergroup:drwxr-xr-x
at
{code}
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532794#comment-15532794
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1812
.Tests failed: 0
.Tests errors: 3
.The patch failed the following testcases:
.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3340/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530481#comment-15530481
]
Abhishek Bafna commented on OOZIE-2613:
---
Does these following documentation useful to this issue:
https://cwiki.apache.org/confluence/display/Hive/HCatalog+Authorization
https://cwiki.apache.org/confluence/display/Hive/Permission+Inheritance+in+Hive
I tried setting {{hive.warehouse.subdir.inherit.perms}} in the
{{initMetastoreServerConf}} and {{startMetastoreServer}} methods, but did not
help.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530354#comment-15530354 ] Robert Kanter commented on OOZIE-2613: -- I tried adding some UGI stuff around the server and client to run as the test user, but that didn't make a difference. AFAIK, the metastore allows multiple users to do things so there should be some way to do this. [~rohini], any ideas? > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528880#comment-15528880 ] Abhishek Bafna commented on OOZIE-2613: --- Yes, i.e. the issue I faced and went for a workaround to get it working. Though I also did not like the solution and would favor a cleaner way than what I did. I am looking into if we can specify some property while starting the metastore server or property while working with database/tables/partitions. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528556#comment-15528556
]
Robert Kanter commented on OOZIE-2613:
--
It seems to be that the underlying problem here is that most of the tests do
stuff as the "test" user, but the hcat things seem to be done as the JVM user.
I tried changing the new {{XHCatTestCase#getTestUser}} to return the JVM user
(the original behavior before this patch) and all tests seemed to work except
for {{TestFsActionExecutor#testDeleteHcat}} because the test user didn't have
permissions to delete a file owned by the JVM user. I don't know enough about
HCat, but is there some way to change the owner when creating a partition? A
fix for that would be less invasive than changing the user in a bunch of places
and the FS user.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517079#comment-15517079 ] Abhishek Bafna commented on OOZIE-2613: --- [~rkanter] and [~rohini] Does this looks good from Oozie 4.3.0 perspective. Thanks. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch, OOZIE-2613-07.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509965#comment-15509965
]
Abhishek Bafna commented on OOZIE-2613:
---
Hi [~rkanter], I have made the changes and submitted the patch. It should work
for both {{hadoop-1}} and {{hadoop-2}} profiles. There is one testcase I am not
able to get it working:
{{org.apache.oozie.action.hadoop.TestJavaActionExecutor.testACLModifyJob}} for
both the profile.
{{TestJavaActionExecutor.testACLModifyJob}} is failing because {{FileSystem}}
is initialized with the {{test}} user and launcher job is launched with
{{user.name}} (due to {{XHCatTestCase#getTestUser}}, added into this patch).
As usual Jenkins failed to post the results here. Link:
https://builds.apache.org/job/oozie-trunk-precommit-build/3311
Please advise, How the above testcase can be fixed or what should be we doing
about it?
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch, OOZIE-2613-07.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508038#comment-15508038
]
Robert Kanter commented on OOZIE-2613:
--
A test is still failing for me with the hadoop-2 profile:
{noformat}
---
Test set: org.apache.oozie.dependency.TestHCatURIHandler
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.789 sec <<<
FAILURE!
testExists(org.apache.oozie.dependency.TestHCatURIHandler) Time elapsed: 0.004
sec <<< ERROR!
org.apache.oozie.service.HCatAccessorException: E1501: Error in getting HCat
Access [org.apache.hive.hcatalog.common.HCatException : 9001 : Exception
occurred while processing HCat request : MetaException while dropping
partition.. Cause : MetaException(message:Got exception:
org.apache.hadoop.security.AccessControlException Permission denied: user=test,
access=WRITE,
inode="/Users/rkanter/dev/oozie-git/core/target/test-data/oozietests/org.apache.oozie.dependency.TestHCatURIHandler/testExists/db1/table1/year=2012/month=12/dt=04":rkanter:supergroup:drwxr-xr-x
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkFsPermission(FSPermissionChecker.java:265)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:251)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:232)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:179)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:5497)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.deleteInternal(FSNamesystem.java:3342)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.deleteInt(FSNamesystem.java:3296)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.delete(FSNamesystem.java:3280)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.delete(NameNodeRpcServer.java:727)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.delete(ClientNamenodeProtocolServerSideTranslatorPB.java:547)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007)
)]
at
org.apache.oozie.dependency.HCatURIHandler.delete(HCatURIHandler.java:201)
at
org.apache.oozie.dependency.TestHCatURIHandler.testExists(TestHCatURIHandler.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:24)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.hive.hcatalog.common.HCatException : 9001 : Exception
occurred while processing HCat request : MetaException while dropping
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507526#comment-15507526 ] Abhishek Bafna commented on OOZIE-2613: --- Ping: [~rohini] and [~rkanter] > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna >Priority: Blocker > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15499465#comment-15499465 ] Abhishek Bafna commented on OOZIE-2613: --- All the failed and error testcases passes locally. :) > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, > OOZIE-2613-06.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15498332#comment-15498332
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1804
.Tests failed: 5
.Tests errors: 3
.The patch failed the following testcases:
. testMain(org.apache.oozie.action.hadoop.TestHiveMain)
. testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
. testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
. testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
. testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3288/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch,
> OOZIE-2613-06.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497441#comment-15497441
]
Robert Kanter commented on OOZIE-2613:
--
This breaks unit tests with the {{hadoop-2}} profile. I know we don't run
those with the Hadoop QA Jenkins thing, but we do want those to work given that
most users are using Hadoop 2 (and when we drop Hadoop 1 eventually).
In CDH, we had to make these changes (we use a Hive based on 1.1.0 or later):
https://github.com/cloudera/oozie/commit/ea9e9f41abcd1ac07e9ed29900f14b52e966d87b
I think the important parts are the code removed in {{MiniHCatServer}} and
{{MiniHS2}}. Though we'll need to allow that code to run with Hive 0.13 but
not with 1.2.0.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496946#comment-15496946
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1804
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3282/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496427#comment-15496427
]
Abhishek Bafna commented on OOZIE-2613:
---
[~rkanter] For testing, I am executing hive and hive2 examples packaged with
Oozie and some custom Hive workflows. Using {{hadoop-2}} and {{uber}} profile
for preparing the tar.
{code}
bin/mkdistro.sh -DskipTests -Phadoop-2,uber
{code}
The reason for no code change is that, It is keeping the same hive version for
{{hadoop-1}} profile, which is explicitly defined in the profile along with
required {{jline}} version. So the upgrade is happening for the all the other
profiles. I have mentioned same in the last few comments while uploading the
patch earlier.
I will upload re-base and updated patch soon. Thanks.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495057#comment-15495057 ] Robert Kanter commented on OOZIE-2613: -- This seems good to me. [~abhishekbafna], how much testing have you done? It's a little surprising that we don't need any code changes to go from Hive 0.13.1 to 1.2.0. Also, you'll need to do some minor refactoring because of OOZIE-2530. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494890#comment-15494890 ] Robert Kanter commented on OOZIE-2613: -- I think it's fine to drop it in 4.3 (I assume that's what you meant, not 4.2). > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472698#comment-15472698
]
Abhishek Bafna commented on OOZIE-2613:
---
[~rkanter] Thanks for the feedback and information. I will create a separate
Jira for the that.
[~asasvari] As per the above comment, we can ignore the {{hadoop-0.23}}
profile. Thanks for your feedback and review. Please let me know, you have any
other suggestions.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15471229#comment-15471229 ] Robert Kanter commented on OOZIE-2613: -- If it's not easy to get this working with the hadoop 0.23 profile, it might make sense to just drop the profile (though probably as a separate JIRA for organization's sake). I imagine nobody is using it at this point. And we've certainly not been testing it. IIRC, it was originally added by Yahoo! long ago when they were using it, but they're on Hadoop 2.x now. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470567#comment-15470567
]
Abhishek Bafna commented on OOZIE-2613:
---
[~asasvari] I was looking into the {{hadoop-0.23}} profile. It does not
compile. There is compilation errors in the {{TestJavaActionExecutor}} class. I
am not sure, If I am missing something while compiling or nobody observed. It
might require a separate jira to fix that, in case if it is a issue.
cc: [~rkanter]
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470239#comment-15470239 ] Attila Sasvari commented on OOZIE-2613: --- Thanks [~abhishekbafna] for the update. Looks good to me, but I have some remarks. How do we plan to handle profile hadoop-0.23? If that profile is selected, then hive 1.2 would be used, eventually running into the same problem as with hadoop-1? Once we have hive 1.2, OOZIE-2621 can be implemented. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15454191#comment-15454191
]
Abhishek Bafna commented on OOZIE-2613:
---
[~asasvari] Can you please refer my last comment and patch
{{OOZIE-2613-03.patch}} for the review. I have uploaded the same into RB as
well. Previously I forgot to update the patch there. Thanks.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445614#comment-15445614 ] Abhishek Bafna commented on OOZIE-2613: --- Testcase failure is intermittent. Test passes locally. > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch, OOZIE-2613-03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445568#comment-15445568
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1798
.Tests failed: 0
.Tests errors: 1
.The patch failed the following testcases:
.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3248/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch, OOZIE-2613-03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445087#comment-15445087
]
Abhishek Bafna commented on OOZIE-2613:
---
[~asasvari] Thanks for the suggestion.
Uploading patch {{OOZIE-2613-03.patch}}.
The hive version for profile {{hadoop-1}} is same. The {{hive.version}} and
{{jline.version}} are explicitly set into the hadoop-1 profile.
{code}
0.13.1
0.9.94
{code}
For the rest, hive version is {{1.2.0}} and jline version {{2.12}}.
As currently we are running the Oozie UT with default {{hadoop-1}} profile,
{{hive-1.2.0}} specific changes for running hive and some other UT's are more
made.
Tested the Hive and Hive2 examples with Oozie tar build using
{{-Phadoop-2,uber}}.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426674#comment-15426674 ] Attila Sasvari commented on OOZIE-2613: --- [~abhishekbafna] Can you maybe impersonate the test user or adjust some FSPermission-s? I am also fine with not updating hive version for hadoop-1 for now (mainly because this profile will be removed sooner or later; it is not really used by a the community as far as I understand). > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: Abhishek Bafna >Assignee: Abhishek Bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, > OOZIE-2613-02.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426216#comment-15426216
]
Abhishek Bafna commented on OOZIE-2613:
---
I am not able to get these two testcases working. I can use some help/feedback
from the fellow developers in the community.
{noformat}
org.apache.oozie.action.hadoop.TestJavaActionExecutor.testACLModifyJob
org.apache.oozie.action.hadoop.TestHiveMain.testMain
{noformat}
{{TestJavaActionExecutor.testACLModifyJob}} is failing because FileSystem is
initialized with the {{test}} user and launcher job is launched with
{{user.name}} (due to {{XHCatTestCase#getTestUser}}, added into this patch).
The Hive testcase works fine with hadoop-2 profile, but fails with hadoop-1
profile.
{noformat}
2016-08-18 14:43:47,507 [main] ERROR org.apache.hadoop.hive.ql.exec.Task -
Failed with exception Unable to rename:
hdfs://localhost:56649/user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output/.hive-staging_hive_2016-08-18_14-41-58_397_1680638062022362363-1/-ext-1
to: /user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output
org.apache.hadoop.hive.ql.metadata.HiveException: Unable to rename:
hdfs://localhost:56649/user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output/.hive-staging_hive_2016-08-18_14-41-58_397_1680638062022362363-1/-ext-1
to: /user/test/95bd1a4c-2629-47bd-a347-f3901b757832/output
at org.apache.hadoop.hive.ql.exec.MoveTask.moveFile(MoveTask.java:114)
at org.apache.hadoop.hive.ql.exec.MoveTask.execute(MoveTask.java:222)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:88)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1650)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1409)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1192)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1059)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1049)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:213)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:165)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:376)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:311)
at
org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:409)
at org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:425)
at
org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:714)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:621)
at org.apache.oozie.action.hadoop.HiveMain.runHive(HiveMain.java:334)
at org.apache.oozie.action.hadoop.HiveMain.run(HiveMain.java:311)
at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:49)
at org.apache.oozie.action.hadoop.HiveMain.main(HiveMain.java:69)
at
org.apache.oozie.action.hadoop.TestHiveMain.call(TestHiveMain.java:138)
at
org.apache.oozie.action.hadoop.TestHiveMain.call(TestHiveMain.java:34)
at
org.apache.oozie.action.hadoop.MainTestCase$1.run(MainTestCase.java:33)
at
org.apache.oozie.action.hadoop.MainTestCase$1.run(MainTestCase.java:31)
at java.security.AccessController.doPrivileged(Native Method)
{noformat}
For the hadoop-1, would it be a good idea to keep the hive version same as
{{hive-0.13.1}}.
cc: [~rkanter] [~jaydeepvishwakarma] [~puru] [~rohini] [~asasvari] [~gezapeti]
[~satishsaley]
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424457#comment-15424457
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 6 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1793
.Tests failed: 1
.Tests errors: 1
.The patch failed the following testcases:
. testMain(org.apache.oozie.action.hadoop.TestHiveMain)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3230/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch,
> OOZIE-2613-02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419047#comment-15419047
]
Hadoop QA commented on OOZIE-2613:
--
Testing JIRA OOZIE-2613
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1792
.Tests failed: 1
.Tests errors: 3
.The patch failed the following testcases:
. testMain(org.apache.oozie.action.hadoop.TestHiveMain)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3226/
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[ https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409836#comment-15409836 ] Taklon Stephen Wu commented on OOZIE-2613: -- Thanks for including my change > Upgrade hive version from 0.13.1 to 1.2.0 > - > > Key: OOZIE-2613 > URL: https://issues.apache.org/jira/browse/OOZIE-2613 > Project: Oozie > Issue Type: Bug > Components: core >Reporter: abhishek bafna >Assignee: abhishek bafna > Fix For: 4.3.0 > > Attachments: OOZIE-2613-00.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0
[
https://issues.apache.org/jira/browse/OOZIE-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409093#comment-15409093
]
abhishek bafna commented on OOZIE-2613:
---
The patch includes the changes from OOZIE-2618, otherwise hive2 example fails
for {{HiveConf}} CNF exception.
> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
> Issue Type: Bug
> Components: core
>Reporter: abhishek bafna
>Assignee: abhishek bafna
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
