[ 
https://issues.apache.org/jira/browse/HIVE-29684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092591#comment-18092591
 ] 

Stamatis Zampetakis commented on HIVE-29684:
--------------------------------------------

Below the failing SQL query formatted for readability:
{code:sql}
select "PARTITIONS"."PART_ID"
from "PARTITIONS"
inner join "TBLS" 
    on "PARTITIONS"."TBL_ID" = "TBLS"."TBL_ID" and "TBLS"."TBL_NAME" = ?
inner join "DBS" 
    on "TBLS"."DB_ID" = "DBS"."DB_ID" and "DBS"."NAME" = ?
inner join "PARTITION_KEY_VALS" "FILTER1" 
    on "FILTER1"."PART_ID" = "PARTITIONS"."PART_ID" and "FILTER1"."INTEGER_IDX" 
= 1
where "DBS"."CTLG_NAME" = ?
  and (((case when 
      "FILTER1"."PART_KEY_VAL" <> ? 
          and "TBLS"."TBL_NAME" = ? 
          and "DBS"."NAME" = ? 
          and "DBS"."CTLG_NAME" = ? 
          and "FILTER1"."PART_ID" = "PARTITIONS"."PART_ID" 
          and "FILTER1"."INTEGER_IDX" = 1 
      then cast("FILTER1"."PART_KEY_VAL" as date)
      else null end) = ? 
            and "PARTITIONS"."PART_NAME" like ?))
order by "PART_NAME" asc
{code}

The parameters in the input are the following:
{noformat}
[tab1_n3, default, hive, __HIVE_DEFAULT_PARTITION__, tab1_n3, default, hive, 
2008-01-01, %/day=2008-01-01%]
{noformat}

According to the stacktrace the part of SQL that probably fails is:
{code:java}
then cast("FILTER1"."PART_KEY_VAL" as date)
{code}



> Intermittent failures in partition_type_check
> ---------------------------------------------
>
>                 Key: HIVE-29684
>                 URL: https://issues.apache.org/jira/browse/HIVE-29684
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Illia Barbashov
>            Assignee: Illia Barbashov
>            Priority: Major
>         Attachments: Screenshot 2026-06-25 at 12.36.57.png, log-1.txt, 
> org.apache.hadoop.hive.cli.split18.TestMiniLlapLocalCliDriver-output-save.txt.gz
>
>
> [^log.txt]
> !Screenshot 2026-06-25 at 12.36.57.png!
> Occasional SemanticException in query tests that might be caused by race 
> condition in LLAP working threads. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to