You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@doris.apache.org by 陈明雨 <mo...@163.com> on 2020/11/25 01:33:10 UTC
Re:Re: [Proposal] Whether to consider prohibit partition column to
be defined to "allow null" when create table
In most case, the null value of a partition column is meaning less and hard to understand.
So I agree to prohibit partition column to be defined to "allow null" when create table
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
在 2020-10-29 17:00:45，"ling miao" <li...@apache.org> 写道：
>I agree to force the partition column to not be empty when creating the
>table.
>But I have a question, under what circumstances will the partition column
>data of the business side be null and the user wants to keep this data at
>the same time ?
>
>Ling Miao
>
>Xinyi Zou <zo...@foxmail.com> 于2020年10月29日周四 下午4:26写道：
>
>> The null value to be a partition value is very confusing.
>>
>>
>> Currently, partition column can be defined as "allow null" when create
>> table. the null value is stored in the partition with MIN_VALUE lower
>> bound. But if that partition is dropped, the null value can not be loaded.
>> So I think it is not a good way to solve the problem.
>>
>>
>>
>> Is it necessary to allow null value to be a partition value? If the
>> null partition column is not supported，how to deal with the current
>> existing table containing null values?
>>
>>
>>
>> We have discussed it in the
>> https://github.com/apache/incubator-doris/pull/4735 before this
>>
>>
>> Xinyi Zou