Re: Fallback Encoding for Very Sparse or Sorted Datasets

This is by design. I guess it benefits sequential scan where the dictionary page is read first and then followed by its encoded indices in the data pages. Otherwise we need to seek anyway. Good, then it shouldn't cause problems when putting the dictionary after all-null pages I think that

Re: Fallback Encoding for Very Sparse or Sorted Datasets

Hi Gang, thanks for your reply. On 01.03.23 03:09, Gang Wu wrote: If at least one record in the beginning 2 rows is not null, then the encoded size will be much better. That is the workaround I have been using for the past weeks, although my tests show that at least two values are

Fallback Encoding for Very Sparse or Sorted Datasets

Hello everyone! First of all, I hope I'm in the right place. The contribution guidelines directed me here after I discovered the registration in the Jira tracker is closed. I'm a Ph.D. student at RPTU Kaiserslautern-Landau, and my current research revolves around sorting-based improvements to