You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Taraka Rama Rao Lethavadla (Jira)" <ji...@apache.org> on 2023/04/28 07:39:00 UTC

[jira] [Commented] (HIVE-26827) Add configs in error message to workaround predicate issue with Parquet on TIMESTAMP data type

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

Taraka Rama Rao Lethavadla commented on HIVE-26827:
---------------------------------------------------

[Attila Turoczy|https://github.com/aturoczy], [~veghlaci05] Thanks for the review and merge. 

> Add configs in error message to workaround predicate issue with Parquet on TIMESTAMP data type
> ----------------------------------------------------------------------------------------------
>
>                 Key: HIVE-26827
>                 URL: https://issues.apache.org/jira/browse/HIVE-26827
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Taraka Rama Rao Lethavadla
>            Assignee: Taraka Rama Rao Lethavadla
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The below query fails with error
> {noformat}
> select * from db.parquet_table_with_timestamp where created_date_utc between
> '2022-11-05 00:01:01' and '2022-11-08 23:59:59'{noformat}
>  
> We can workaround the issue below
>  
> {noformat}
> 2022-11-10 06:43:36,751 [ERROR] [TezChild] |read.ParquetFilterPredicateConverter|: fail to build predicate filter leaf with errors org.apache.hadoop.hive.ql.metadata.HiveException: Conversion to Parquet FilterPredicate not supported for TIMESTAMP{noformat}
> by setting configs at session level
>  # set hive.optimize.index.filter=false;
>  # set hive.optimize.ppd=false;
> As part of this Jira proposing to add these config info to the above message so that who ever encounter this problem can try the workaround
>  



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