[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[
https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687598#comment-16687598
]
Hive QA commented on HIVE-20708:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12948251/HIVE-20708.03
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 15543 tests
executed
*Failed tests:*
{noformat}
org.apache.hive.jdbc.TestSSL.testMetastoreConnectionWrongCertCN (batchId=258)
org.apache.hive.jdbc.TestSSL.testSSLConnectionWithProperty (batchId=258)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14939/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14939/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14939/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12948251 - PreCommit-HIVE-Build
> Load (dumped) an external table as an external table on target with the same
> location as on the source
> --
>
> Key: HIVE-20708
> URL: https://issues.apache.org/jira/browse/HIVE-20708
> Project: Hive
> Issue Type: Improvement
> Components: repl
>Reporter: Ashutosh Bapat
>Assignee: Ashutosh Bapat
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-20708.01, HIVE-20708.02, HIVE-20708.03
>
>
> External tables are currently mapped to managed tables on target. A lot of
> jobs in user environment are dependent upon locations specified in external
> table definitions to run, hence, the path for external tables on the target
> and on the source are expected to be the same. An external table being loaded
> as a managed table makes it difficult for failover (Controlled Failover) /
> failback since there is no option of moving data from managed to external
> table. So the external table replicated to target cluster needs to be kept as
> external table with same location as on the source.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[
https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687559#comment-16687559
]
Hive QA commented on HIVE-20708:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
32s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
38s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 3m
44s{color} | {color:blue} ql in master has 2316 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
14s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
15s{color} | {color:green} The patch hive-unit passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
38s{color} | {color:green} ql: The patch generated 0 new + 218 unchanged - 1
fixed = 218 total (was 219) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
16s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
13s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 27m 3s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc findbugs checkstyle compile |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-14939/dev-support/hive-personality.sh
|
| git revision | master / 6fbdf37 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: itests/hive-unit ql U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-14939/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Load (dumped) an external table as an external table on target with the same
> location as on the source
> --
>
> Key: HIVE-20708
> URL: https://issues.apache.org/jira/browse/HIVE-20708
> Project: Hive
> Issue Type: Improvement
> Components: repl
>Reporter: Ashutosh Bapat
>Assignee: Ashutosh Bapat
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-20708.01, HIVE-20708.02, HIVE-20708.03
>
>
> External tables are currently mapped to managed tables on target. A lot of
> jobs in user environment are dependent upon locations specified in external
> table definitions to run, hence, the path for external tables on the target
> and on the source are expected to be the same. An external table being loaded
> as a managed table makes it difficult for failover (Controlled Failover) /
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[ https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668913#comment-16668913 ] Sankar Hariappan commented on HIVE-20708: - [~ashutosh.bapat] I posted few comments in the PR. Please take a look. > Load (dumped) an external table as an external table on target with the same > location as on the source > -- > > Key: HIVE-20708 > URL: https://issues.apache.org/jira/browse/HIVE-20708 > Project: Hive > Issue Type: Improvement > Components: repl >Reporter: Ashutosh Bapat >Assignee: Ashutosh Bapat >Priority: Major > Labels: pull-request-available > Attachments: HIVE-20708.01, HIVE-20708.02 > > > External tables are currently mapped to managed tables on target. A lot of > jobs in user environment are dependent upon locations specified in external > table definitions to run, hence, the path for external tables on the target > and on the source are expected to be the same. An external table being loaded > as a managed table makes it difficult for failover (Controlled Failover) / > failback since there is no option of moving data from managed to external > table. So the external table replicated to target cluster needs to be kept as > external table with same location as on the source. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[ https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668348#comment-16668348 ] Ashutosh Bapat commented on HIVE-20708: --- [~sankarh], [~maheshk114], can you plese review the changes. > Load (dumped) an external table as an external table on target with the same > location as on the source > -- > > Key: HIVE-20708 > URL: https://issues.apache.org/jira/browse/HIVE-20708 > Project: Hive > Issue Type: Improvement > Components: repl >Reporter: Ashutosh Bapat >Assignee: Ashutosh Bapat >Priority: Major > Labels: pull-request-available > Attachments: HIVE-20708.01, HIVE-20708.02 > > > External tables are currently mapped to managed tables on target. A lot of > jobs in user environment are dependent upon locations specified in external > table definitions to run, hence, the path for external tables on the target > and on the source are expected to be the same. An external table being loaded > as a managed table makes it difficult for failover (Controlled Failover) / > failback since there is no option of moving data from managed to external > table. So the external table replicated to target cluster needs to be kept as > external table with same location as on the source. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[ https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668349#comment-16668349 ] Ashutosh Bapat commented on HIVE-20708: --- [~sankarh], [~maheshk114], can you please review the changes. > Load (dumped) an external table as an external table on target with the same > location as on the source > -- > > Key: HIVE-20708 > URL: https://issues.apache.org/jira/browse/HIVE-20708 > Project: Hive > Issue Type: Improvement > Components: repl >Reporter: Ashutosh Bapat >Assignee: Ashutosh Bapat >Priority: Major > Labels: pull-request-available > Attachments: HIVE-20708.01, HIVE-20708.02 > > > External tables are currently mapped to managed tables on target. A lot of > jobs in user environment are dependent upon locations specified in external > table definitions to run, hence, the path for external tables on the target > and on the source are expected to be the same. An external table being loaded > as a managed table makes it difficult for failover (Controlled Failover) / > failback since there is no option of moving data from managed to external > table. So the external table replicated to target cluster needs to be kept as > external table with same location as on the source. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[
https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657692#comment-16657692
]
Hive QA commented on HIVE-20708:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12944771/HIVE-20708.02
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15111 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14580/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14580/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14580/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12944771 - PreCommit-HIVE-Build
> Load (dumped) an external table as an external table on target with the same
> location as on the source
> --
>
> Key: HIVE-20708
> URL: https://issues.apache.org/jira/browse/HIVE-20708
> Project: Hive
> Issue Type: Improvement
> Components: repl
>Reporter: Ashutosh Bapat
>Assignee: Ashutosh Bapat
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-20708.01, HIVE-20708.02
>
>
> External tables are currently mapped to managed tables on target. A lot of
> jobs in user environment are dependent upon locations specified in external
> table definitions to run, hence, the path for external tables on the target
> and on the source are expected to be the same. An external table being loaded
> as a managed table makes it difficult for failover (Controlled Failover) /
> failback since there is no option of moving data from managed to external
> table. So the external table replicated to target cluster needs to be kept as
> external table with same location as on the source.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[
https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657682#comment-16657682
]
Hive QA commented on HIVE-20708:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
2s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 9m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
5s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
49s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
44s{color} | {color:blue} ql in master has 2318 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
38s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
36s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 34m 46s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc findbugs checkstyle compile |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-14580/dev-support/hive-personality.sh
|
| git revision | master / 4a7de47 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: itests/hive-unit ql U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-14580/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Load (dumped) an external table as an external table on target with the same
> location as on the source
> --
>
> Key: HIVE-20708
> URL: https://issues.apache.org/jira/browse/HIVE-20708
> Project: Hive
> Issue Type: Improvement
> Components: repl
>Reporter: Ashutosh Bapat
>Assignee: Ashutosh Bapat
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-20708.01, HIVE-20708.02
>
>
> External tables are currently mapped to managed tables on target. A lot of
> jobs in user environment are dependent upon locations specified in external
> table definitions to run, hence, the path for external tables on the target
> and on the source are expected to be the same. An external table being loaded
> as a managed table makes it difficult for failover (Controlled Failover) /
> failback since there is no option of moving data from managed to external
> table. So the external table replicated to target cluster needs to be kept as
> external table with same location as on the source.
--
This message
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[
https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652300#comment-16652300
]
Hive QA commented on HIVE-20708:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12944081/HIVE-20708.01
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 15085 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[repl_2_exim_basic]
(batchId=84)
org.apache.hadoop.hive.ql.parse.TestReplicationScenariosAcrossInstances.testDumpExternalTableSetFalse
(batchId=245)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14504/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14504/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14504/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12944081 - PreCommit-HIVE-Build
> Load (dumped) an external table as an external table on target with the same
> location as on the source
> --
>
> Key: HIVE-20708
> URL: https://issues.apache.org/jira/browse/HIVE-20708
> Project: Hive
> Issue Type: Improvement
> Components: repl
>Reporter: Ashutosh Bapat
>Assignee: Ashutosh Bapat
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-20708.01
>
>
> External tables are currently mapped to managed tables on target. A lot of
> jobs in user environment are dependent upon locations specified in external
> table definitions to run, hence, the path for external tables on the target
> and on the source are expected to be the same. An external table being loaded
> as a managed table makes it difficult for failover (Controlled Failover) /
> failback since there is no option of moving data from managed to external
> table. So the external table replicated to target cluster needs to be kept as
> external table with same location as on the source.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[
https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652236#comment-16652236
]
Hive QA commented on HIVE-20708:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
36s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
41s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
7s{color} | {color:blue} ql in master has 2318 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
24s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
46s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
17s{color} | {color:red} itests/hive-unit: The patch generated 5 new + 134
unchanged - 0 fixed = 139 total (was 134) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
41s{color} | {color:red} ql: The patch generated 3 new + 204 unchanged - 0
fixed = 207 total (was 204) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
25s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 30m 11s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc findbugs checkstyle compile |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-14504/dev-support/hive-personality.sh
|
| git revision | master / 0f2f999 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-14504/yetus/diff-checkstyle-itests_hive-unit.txt
|
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-14504/yetus/diff-checkstyle-ql.txt
|
| modules | C: itests/hive-unit ql U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-14504/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Load (dumped) an external table as an external table on target with the same
> location as on the source
> --
>
> Key: HIVE-20708
> URL: https://issues.apache.org/jira/browse/HIVE-20708
> Project: Hive
> Issue Type: Improvement
> Components: repl
>Reporter: Ashutosh Bapat
>Assignee: Ashutosh Bapat
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-20708.01
>
>
> External tables are currently mapped to managed tables on target. A lot of
> jobs in user environment are dependent upon locations specified in external
> table
[jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
[ https://issues.apache.org/jira/browse/HIVE-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651336#comment-16651336 ] ASF GitHub Bot commented on HIVE-20708: --- GitHub user ashutosh-bapat opened a pull request: https://github.com/apache/hive/pull/447 HIVE-20708: Load an external table as an external table on target with the same location as on the source Dump an external table as an external table. When loading an external table set the location of the target table same as the location of source, but relative to the file system of the target location. IOW, the scheme, authority of the target location is same as the target file system but the path relative to the file system is same as the source. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ashutosh-bapat/hive hive20708 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/hive/pull/447.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #447 commit c076bbbd2b0fd1b193ac51a1595911a80324b923 Author: Ashutosh Bapat Date: 2018-10-15T05:09:05Z HIVE-20708: Load an external table as an external table on target with the same location as on the source Dump an external table as an external table. When loading an external table set the location of the target table same as the location of source, but relative to the file system of the target location. IOW, the scheme, authority of the target location is same as the target file system but the path relative to the file system is same as the source. > Load (dumped) an external table as an external table on target with the same > location as on the source > -- > > Key: HIVE-20708 > URL: https://issues.apache.org/jira/browse/HIVE-20708 > Project: Hive > Issue Type: Improvement > Components: repl >Reporter: Ashutosh Bapat >Assignee: Ashutosh Bapat >Priority: Major > Labels: pull-request-available > > External tables are currently mapped to managed tables on target. A lot of > jobs in user environment are dependent upon locations specified in external > table definitions to run, hence, the path for external tables on the target > and on the source are expected to be the same. An external table being loaded > as a managed table makes it difficult for failover (Controlled Failover) / > failback since there is no option of moving data from managed to external > table. So the external table replicated to target cluster needs to be kept as > external table with same location as on the source. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
