[jira] [Updated] (HIVE-6815) Version of the HIVE-6374 for Hive 0.13
[ https://issues.apache.org/jira/browse/HIVE-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6815: --- Resolution: Invalid Status: Resolved (was: Patch Available) Not needed. Version of the HIVE-6374 for Hive 0.13 -- Key: HIVE-6815 URL: https://issues.apache.org/jira/browse/HIVE-6815 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.13.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.14.0 Attachments: hive-6374.branch-0.13.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Status: Patch Available (was: In Progress) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.12.0, 0.11.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.3.patch, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Attachment: hive-6374.3.patch Updated after sync with latest trunk Fixed bug with wrong casing of table/index/db paths Please review and vote! (Note: the TestMinimrCliDriver tests fail even without the patch, therefore they are not related to this change) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.3.patch, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Status: In Progress (was: Patch Available) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.12.0, 0.11.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.3.patch, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Status: Patch Available (was: In Progress) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.12.0, 0.11.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6813) Version of the HIVE-6374 for Hive 0.11
[ https://issues.apache.org/jira/browse/HIVE-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6813: --- Status: Open (was: Patch Available) Version of the HIVE-6374 for Hive 0.11 -- Key: HIVE-6813 URL: https://issues.apache.org/jira/browse/HIVE-6813 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.11.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.11.0 Attachments: hive-6374.branch-0.11.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6814) Version of the HIVE-6374 for Hive 0.12
[ https://issues.apache.org/jira/browse/HIVE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6814: --- Status: Open (was: Patch Available) Version of the HIVE-6374 for Hive 0.12 -- Key: HIVE-6814 URL: https://issues.apache.org/jira/browse/HIVE-6814 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.12.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.12.0 Attachments: hive-6374.branch-0.12.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (HIVE-6813) Version of the HIVE-6374 for Hive 0.11
[ https://issues.apache.org/jira/browse/HIVE-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky resolved HIVE-6813. Resolution: Invalid Opened by mistake Version of the HIVE-6374 for Hive 0.11 -- Key: HIVE-6813 URL: https://issues.apache.org/jira/browse/HIVE-6813 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.11.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.11.0 Attachments: hive-6374.branch-0.11.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (HIVE-6814) Version of the HIVE-6374 for Hive 0.12
[ https://issues.apache.org/jira/browse/HIVE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky resolved HIVE-6814. Resolution: Invalid Created by mistake Version of the HIVE-6374 for Hive 0.12 -- Key: HIVE-6814 URL: https://issues.apache.org/jira/browse/HIVE-6814 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.12.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.12.0 Attachments: hive-6374.branch-0.12.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6813) Version of the HIVE-6374 for Hive 0.11
Benjamin Zhitomirsky created HIVE-6813: -- Summary: Version of the HIVE-6374 for Hive 0.11 Key: HIVE-6813 URL: https://issues.apache.org/jira/browse/HIVE-6813 Project: Hive Issue Type: Sub-task Affects Versions: 0.11.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.11.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6814) Version of the HIVE-6374 for Hive 0.12
Benjamin Zhitomirsky created HIVE-6814: -- Summary: Version of the HIVE-6374 for Hive 0.12 Key: HIVE-6814 URL: https://issues.apache.org/jira/browse/HIVE-6814 Project: Hive Issue Type: Sub-task Affects Versions: 0.12.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.12.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6815) Version of the HIVE-6374 for Hive 0.13
Benjamin Zhitomirsky created HIVE-6815: -- Summary: Version of the HIVE-6374 for Hive 0.13 Key: HIVE-6815 URL: https://issues.apache.org/jira/browse/HIVE-6815 Project: Hive Issue Type: Sub-task Affects Versions: 0.13.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.13.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Attachment: hive-6374.1.patch Test cleanup fixed (was not failing the test, but however it is nicer...) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6813) Version of the HIVE-6374 for Hive 0.11
[ https://issues.apache.org/jira/browse/HIVE-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6813: --- Status: Patch Available (was: Open) Version of the HIVE-6374 for Hive 0.11 -- Key: HIVE-6813 URL: https://issues.apache.org/jira/browse/HIVE-6813 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.11.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.11.0 Attachments: hive-6374.branch-0.11.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6813) Version of the HIVE-6374 for Hive 0.11
[ https://issues.apache.org/jira/browse/HIVE-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6813: --- Attachment: hive-6374.branch-0.11.patch Version of the HIVE-6374 for Hive 0.11 -- Key: HIVE-6813 URL: https://issues.apache.org/jira/browse/HIVE-6813 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.11.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.11.0 Attachments: hive-6374.branch-0.11.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6815) Version of the HIVE-6374 for Hive 0.13
[ https://issues.apache.org/jira/browse/HIVE-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6815: --- Attachment: hive-6374.branch-0.13.patch Version of the HIVE-6374 for Hive 0.13 -- Key: HIVE-6815 URL: https://issues.apache.org/jira/browse/HIVE-6815 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.13.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.13.0 Attachments: hive-6374.branch-0.13.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6815) Version of the HIVE-6374 for Hive 0.13
[ https://issues.apache.org/jira/browse/HIVE-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6815: --- Status: Patch Available (was: Open) Version of the HIVE-6374 for Hive 0.13 -- Key: HIVE-6815 URL: https://issues.apache.org/jira/browse/HIVE-6815 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.13.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.13.0 Attachments: hive-6374.branch-0.13.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6814) Version of the HIVE-6374 for Hive 0.12
[ https://issues.apache.org/jira/browse/HIVE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6814: --- Status: Patch Available (was: Open) Version of the HIVE-6374 for Hive 0.12 -- Key: HIVE-6814 URL: https://issues.apache.org/jira/browse/HIVE-6814 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.12.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.12.0 Attachments: hive-6374.branch-0.12.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Status: In Progress (was: Patch Available) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.12.0, 0.11.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6814) Version of the HIVE-6374 for Hive 0.12
[ https://issues.apache.org/jira/browse/HIVE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6814: --- Attachment: hive-6374.branch-0.12.patch Version of the HIVE-6374 for Hive 0.12 -- Key: HIVE-6814 URL: https://issues.apache.org/jira/browse/HIVE-6814 Project: Hive Issue Type: Sub-task Components: CLI Affects Versions: 0.12.0 Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Fix For: 0.12.0 Attachments: hive-6374.branch-0.12.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13957781#comment-13957781 ] Benjamin Zhitomirsky commented on HIVE-6374: CR is available here: https://reviews.apache.org/r/19923/ Thanks to Ashutosh for reminding! Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Assignee: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Affects Version/s: 0.13.0 Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Fix For: 0.11.1 Attachments: Design of the fix HIVE-6374.docx Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Attachment: (was: hive-6385.patch) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Fix For: 0.11.1 Attachments: Design of the fix HIVE-6374.docx Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Attachment: hive-6385.patch Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Fix For: 0.11.1 Attachments: Design of the fix HIVE-6374.docx Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Fix Version/s: (was: 0.11.1) Status: Patch Available (was: Open) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.12.0, 0.11.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Attachment: hive-6374.patch Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0, 0.13.0 Environment: Any Reporter: Benjamin Zhitomirsky Attachments: Design of the fix HIVE-6374.docx, hive-6374.patch Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
Benjamin Zhitomirsky created HIVE-6374: -- Summary: Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.12.0, 0.11.0 Environment: Any Reporter: Benjamin Zhitomirsky Fix For: 0.11.1 Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly
[ https://issues.apache.org/jira/browse/HIVE-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Zhitomirsky updated HIVE-6374: --- Attachment: Design of the fix HIVE-6374.docx More details and description of the fix Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly --- Key: HIVE-6374 URL: https://issues.apache.org/jira/browse/HIVE-6374 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.11.0, 0.12.0 Environment: Any Reporter: Benjamin Zhitomirsky Fix For: 0.11.1 Attachments: Design of the fix HIVE-6374.docx Original Estimate: 168h Remaining Estimate: 168h Create table/index/database and add partition DDL doesn't work properly if all following conditions are true: - Metastore service is used - fs.default.name is specified and it differs from the default one - Location is not specified or specified as a not fully qualified URI The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change). The CR will submitted shortly after tests are done -- This message was sent by Atlassian JIRA (v6.1.5#6160)
