[ https://issues.apache.org/jira/browse/HIVE-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878962#comment-16878962 ]
Hive QA commented on HIVE-21955: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12973674/HIVE-21955.1.branch-1.patch {color:red}ERROR:{color} -1 due to build exiting with an error Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/17863/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17863/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17863/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12973674/HIVE-21955.1.branch-1.patch was found in seen patch url's cache and a test was probably run already on it. Aborting... {noformat} This message is automatically generated. ATTACHMENT ID: 12973674 - PreCommit-HIVE-Build > SearchArgumentImpl generates wrong ExpressionTree in some cases which might > result in loss of data > --------------------------------------------------------------------------------------------------- > > Key: HIVE-21955 > URL: https://issues.apache.org/jira/browse/HIVE-21955 > Project: Hive > Issue Type: Bug > Components: Hive, storage-api > Affects Versions: 1.2.1 > Reporter: Zihao Ye > Assignee: Zihao Ye > Priority: Critical > Labels: pushdown > Attachments: HIVE-21955.1.branch-1.patch, HIVE-21955.branch-1.patch > > > ExpressionBuilder applies `pushDownNot`, `foldMaybe`, `flatten`, > `convertToCNF`, `flatten` and `buildLeafList` in order to form a > non-normalized expression into a CNF expression with the unique leaves. > After an expression is converted to CNF, there might be *more than one > non-leaf nodes which are exactly the same object* in the expression tree. If > this happens, those non-leaf nodes will be visited more than once in > `buildLeafList` function. As a result, a wrong ExpressionTree is generated. > My version is 1.2.1, but it seems that the higher versions are also affected -- This message was sent by Atlassian JIRA (v7.6.3#76005)