[
https://issues.apache.org/jira/browse/HUDI-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sivabalan narayanan updated HUDI-3056:
--------------------------------------
Sprint: Cont' improve - 2022/02/14, Cont' improve - 2022/02/21 (was:
Cont' improve - 2022/02/14)
> Not able to query hudi tables in 0.10.0 with redshift
> -----------------------------------------------------
>
> Key: HUDI-3056
> URL: https://issues.apache.org/jira/browse/HUDI-3056
> Project: Apache Hudi
> Issue Type: Bug
> Components: Usability
> Affects Versions: 0.10.0
> Reporter: sivabalan narayanan
> Assignee: Udit Mehrotra
> Priority: Critical
> Labels: query-engine, sev:critical
>
> Since with 0.10.0 we changed the format of timestamp, redshift is failing to
> read hudi tables created with 0.10.0
>
> I have noticed the instant timestamp length have changed from
> {{yyyyMMddHHmmss}} to {{{}yyyyMMddHHmmssSSS{}}},
> once I tried to use
> 'org.apache.hudi.hadoop.hive.HoodieCombineHiveInputFormat', redshift shows
> 'hudi::ParsedFilename::IsValidCommitTimestamp(
> std::string(ctx.hudi_commit_timestamp))' error, I still have no idea why
> there is nothing return when using
> {{org.apache.hudi.hadoop.HoodieParquetInputFormat}}
> {{}}
> {{Ref issue: [https://github.com/apache/hudi/issues/4283]}}
> {{}}
> {{}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
