flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-13950) should report an error if hive table partition keys are not in the last schema fields
Date Sun, 06 Jun 2021 10:55:01 GMT

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

Flink Jira Bot updated FLINK-13950:
    Labels: auto-deprioritized-critical stale-major  (was: auto-deprioritized-critical)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issues has been marked as Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.

> should report an error if hive table partition keys are not in the last schema fields
> -------------------------------------------------------------------------------------
>                 Key: FLINK-13950
>                 URL: https://issues.apache.org/jira/browse/FLINK-13950
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Hive
>    Affects Versions: 1.9.0, 1.10.0
>            Reporter: Hongtao Zhang
>            Priority: Major
>              Labels: auto-deprioritized-critical, stale-major
> when creating a hive table via hive catalog API, we will build the table schema first
and then optionally we can choose one or more fields as the partition keys when user want
to create partition table. 
> according to hive partition rule, the partition keys should be  last fields of the table.
but now hive catalog create table API didn't report an error when user specify the first /
middle fields of the table schema.
> we should report an error for this scenario

This message was sent by Atlassian Jira

View raw message