[jira] [Commented] (HIVE-16006) Incremental REPL LOAD Inserts doesn't operate on the target database if name differs from source database.
[ https://issues.apache.org/jira/browse/HIVE-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900706#comment-15900706 ] Sankar Hariappan commented on HIVE-16006: - Thank you [~sushanth] for the commit! > Incremental REPL LOAD Inserts doesn't operate on the target database if name > differs from source database. > -- > > Key: HIVE-16006 > URL: https://issues.apache.org/jira/browse/HIVE-16006 > Project: Hive > Issue Type: Sub-task > Components: repl >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan > Fix For: 2.2.0 > > Attachments: HIVE-16006.01.patch, HIVE-16006.02.patch, > HIVE-16006.03.patch > > > During "Incremental Load", it is not considering the database name input in > the command line. Hence load doesn't happen. At the same time, database with > original name is getting modified. > Steps: > 1. INSERT INTO default.tbl values (10, 20); > 2. REPL DUMP default FROM 52; > 3. REPL LOAD replDb FROM '/tmp/dump/1487588522621'; > – This step modifies the default Db instead of replDb. > == > Additional note - this is happening for INSERT events, not other events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HIVE-16006) Incremental REPL LOAD Inserts doesn't operate on the target database if name differs from source database.
[ https://issues.apache.org/jira/browse/HIVE-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900642#comment-15900642 ] Sushanth Sowmyan commented on HIVE-16006: - (Forgot to explicitly mention in previous comment, this patch has my +1. :) ) > Incremental REPL LOAD Inserts doesn't operate on the target database if name > differs from source database. > -- > > Key: HIVE-16006 > URL: https://issues.apache.org/jira/browse/HIVE-16006 > Project: Hive > Issue Type: Sub-task > Components: repl >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan > Fix For: 2.2.0 > > Attachments: HIVE-16006.01.patch, HIVE-16006.02.patch, > HIVE-16006.03.patch > > > During "Incremental Load", it is not considering the database name input in > the command line. Hence load doesn't happen. At the same time, database with > original name is getting modified. > Steps: > 1. INSERT INTO default.tbl values (10, 20); > 2. REPL DUMP default FROM 52; > 3. REPL LOAD replDb FROM '/tmp/dump/1487588522621'; > – This step modifies the default Db instead of replDb. > == > Additional note - this is happening for INSERT events, not other events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HIVE-16006) Incremental REPL LOAD Inserts doesn't operate on the target database if name differs from source database.
[
https://issues.apache.org/jira/browse/HIVE-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891271#comment-15891271
]
Hive QA commented on HIVE-16006:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12855460/HIVE-16006.03.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 10 failed/errored test(s), 10283 tests
executed
*Failed tests:*
{noformat}
TestCommandProcessorFactory - did not produce a TEST-*.xml file (likely timed
out) (batchId=272)
TestDbTxnManager - did not produce a TEST-*.xml file (likely timed out)
(batchId=272)
TestDummyTxnManager - did not produce a TEST-*.xml file (likely timed out)
(batchId=272)
TestHiveInputSplitComparator - did not produce a TEST-*.xml file (likely timed
out) (batchId=272)
TestIndexType - did not produce a TEST-*.xml file (likely timed out)
(batchId=272)
TestSplitFilter - did not produce a TEST-*.xml file (likely timed out)
(batchId=272)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[schema_evol_text_vec_table]
(batchId=147)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14]
(batchId=224)
org.apache.hadoop.hive.cli.TestSparkCliDriver.testCliDriver[vector_between_in]
(batchId=119)
org.apache.hive.beeline.TestBeeLineWithArgs.testQueryProgressParallel
(batchId=212)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/3877/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/3877/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-3877/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 10 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12855460 - PreCommit-HIVE-Build
> Incremental REPL LOAD Inserts doesn't operate on the target database if name
> differs from source database.
> --
>
> Key: HIVE-16006
> URL: https://issues.apache.org/jira/browse/HIVE-16006
> Project: Hive
> Issue Type: Sub-task
> Components: repl
>Reporter: Sankar Hariappan
>Assignee: Sankar Hariappan
> Attachments: HIVE-16006.01.patch, HIVE-16006.02.patch,
> HIVE-16006.03.patch
>
>
> During "Incremental Load", it is not considering the database name input in
> the command line. Hence load doesn't happen. At the same time, database with
> original name is getting modified.
> Steps:
> 1. INSERT INTO default.tbl values (10, 20);
> 2. REPL DUMP default FROM 52;
> 3. REPL LOAD replDb FROM '/tmp/dump/1487588522621';
> – This step modifies the default Db instead of replDb.
> ==
> Additional note - this is happening for INSERT events, not other events.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HIVE-16006) Incremental REPL LOAD Inserts doesn't operate on the target database if name differs from source database.
[ https://issues.apache.org/jira/browse/HIVE-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889479#comment-15889479 ] Sushanth Sowmyan commented on HIVE-16006: - Code-wise, this version fixes the issue correctly, and is the kind of change to ReplicationSpec that I thought was necessary. :) However, from the test that was added, I see that that test succeeds even without these changes. i.e., if I pick only the test change and nothing else, the test still succeeds, which it should not, since this patch is what fixes the bug. Could you look into the test to see why that is? > Incremental REPL LOAD Inserts doesn't operate on the target database if name > differs from source database. > -- > > Key: HIVE-16006 > URL: https://issues.apache.org/jira/browse/HIVE-16006 > Project: Hive > Issue Type: Sub-task > Components: repl >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan > Attachments: HIVE-16006.01.patch, HIVE-16006.02.patch > > > During "Incremental Load", it is not considering the database name input in > the command line. Hence load doesn't happen. At the same time, database with > original name is getting modified. > Steps: > 1. REPL DUMP default FROM 52; > 2. REPL LOAD replDb FROM '/tmp/dump/1487588522621'; > – This step modifies the default Db instead of replDb. > == > Additional note - this is happening for INSERT events, not other events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
