You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Leonard Xu (Jira)" <ji...@apache.org> on 2022/07/08 06:33:00 UTC

[jira] [Assigned] (FLINK-27384) In the Hive dimension table, when the data is changed on the original partition, the create_time configuration does not take effect

     [ https://issues.apache.org/jira/browse/FLINK-27384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonard Xu reassigned FLINK-27384:
----------------------------------

    Assignee: 陈磊

> In the Hive dimension table, when the data is changed on the original partition, the create_time configuration does not take effect
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-27384
>                 URL: https://issues.apache.org/jira/browse/FLINK-27384
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Hive
>    Affects Versions: 1.14.4
>            Reporter: 陈磊
>            Assignee: 陈磊
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2022-04-25-15-46-01-833.png, image-2022-04-25-15-47-54-213.png
>
>
> In the Hive dimension table, when the data is changed on the original partition, the create_time configuration does not take effect.
> !image-2022-04-25-15-46-01-833.png!
> The current table structure directory is as follows:
> !image-2022-04-25-15-47-54-213.png!
> From the above figure, we can know that when hive is a dimension table, it will load the data of dt=2021-04-22, hr=27.
> If a new partition arrives now, the data of the latest partition can be read smoothly. However, if the data is modified on the original partition, theoretically, the data of the modified partition is read, because of the create_time and latest configuration, but this is not the case in practice. The data that was originally loaded is still read.



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