Chun
> Sent: July 20, 2021 2:42
> To: dev@doris.apache.org
> Subject: Re: [Proposal] Support large variable-length string type
>
> This solution we have done some POC internally.
>
> In the current code, this will cause the memory usage to become larger and
> more likely to trig
ly 20, 2021 2:42
To: dev@doris.apache.org
Subject: Re: [Proposal] Support large variable-length string type
This solution we have done some POC internally.
In the current code, this will cause the memory usage to become larger and
more likely to trigger OOM,
also the size of batch will excee
I think the keypoint here is the way to store and visit string columm.
I prefer to do a poc that stores the string column in a separate file and
using rowid to visit it.
If doris store the string column with common columns one file, it may break
some existing assumptions about segment file.
--
This solution we have done some POC internally.
In the current code, this will cause the memory usage to become larger and
more likely to trigger OOM,
also the size of batch will exceed the maximum value of int32 during RPC.
So to use this scheme, you need to design carefully in several places.
Hi All
I want to submit a proposal to support larger string types.
Background
There are currently two types of strings: CHAR and VARCHAR. Char stores
fixed-length strings and VARCHAR stores variable-length strings. The
maximum length of VARCHAR is 65533. This length can meet most demand
scenarios,
