[ 
https://issues.apache.org/jira/browse/HIVE-21172?focusedWorklogId=696446&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-696446
 ]

ASF GitHub Bot logged work on HIVE-21172:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Dec/21 08:42
            Start Date: 15/Dec/21 08:42
    Worklog Time Spent: 10m 
      Work Description: kasakrisz commented on a change in pull request #2857:
URL: https://github.com/apache/hive/pull/2857#discussion_r769380412



##########
File path: 
ql/src/test/results/clientpositive/llap/acid_direct_update_delete_with_merge.q.out
##########
@@ -112,11 +110,13 @@ POSTHOOK: Input: default@transactions@tran_date=20170413
 POSTHOOK: Output: default@merge_tmp_table
 POSTHOOK: Output: default@transactions
 POSTHOOK: Output: default@transactions@tran_date=20170410
-POSTHOOK: Output: default@transactions@tran_date=20170410
 POSTHOOK: Output: default@transactions@tran_date=20170413
 POSTHOOK: Output: default@transactions@tran_date=20170413
 POSTHOOK: Output: default@transactions@tran_date=20170415
 POSTHOOK: Lineage: merge_tmp_table.val EXPRESSION 
[(transactions)t.FieldSchema(name:ROW__ID, 
type:struct<writeId:bigint,bucketId:int,rowId:bigint>, comment:), 
(transactions)t.FieldSchema(name:tran_date, type:string, comment:null), ]
+POSTHOOK: Lineage: transactions PARTITION(tran_date=20170413).id SIMPLE 
[(merge_source)s.FieldSchema(name:id, type:int, comment:null), ]

Review comment:
       same as above




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 696446)
    Time Spent: 50m  (was: 40m)

> DEFAULT keyword handling in MERGE UPDATE clause issues
> ------------------------------------------------------
>
>                 Key: HIVE-21172
>                 URL: https://issues.apache.org/jira/browse/HIVE-21172
>             Project: Hive
>          Issue Type: Sub-task
>          Components: SQL, Transactions
>    Affects Versions: 4.0.0
>            Reporter: Eugene Koifman
>            Assignee: Krisztian Kasa
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> once HIVE-21159 lands, enable {{HiveConf.MERGE_SPLIT_UPDATE}} and run these 
> tests.
> TestMiniLlapLocalCliDriver.testCliDriver[sqlmerge_stats]
>  mvn test -Dtest=TestMiniLlapLocalCliDriver 
> -Dqfile=insert_into_default_keyword.q
> Merge is rewritten as a multi-insert. When Update clause has DEFAULT, it's 
> not properly replaced with a value in the muli-insert - it's treated as a 
> literal
> {noformat}
> INSERT INTO `default`.`acidTable`    -- update clause(insert part)
>  SELECT `t`.`key`, `DEFAULT`, `t`.`value`
>    WHERE `t`.`key` = `s`.`key` AND `s`.`key` > 3 AND NOT(`s`.`key` < 3)
> {noformat}
> See {{LOG.info("Going to reparse <" + originalQuery + "> as \n<" + 
> rewrittenQueryStr.toString() + ">");}} in hive.log
> {{MergeSemanticAnalyzer.replaceDefaultKeywordForMerge()}} is only called in 
> {{handleInsert}} but not {{handleUpdate()}}. Why does issue only show up with 
> {{MERGE_SPLIT_UPDATE}}?
> Once this is fixed, HiveConf.MERGE_SPLIT_UPDATE should be true by default



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to