Closed sadikovi closed 7 years ago
@sunchao please review. Thanks!
@sunchao updated code, so now I just reassign encoding like you suggested, though I have to use mut encoding
in match statement for page. Is this okay?
@sadikovi Yes I think it should be OK: the page is consumed upon usage so this modification won't be an issue.
This PR fixes reading columns with PLAIN_DICTIONARY encoding.
Before the patch, reading of such columns would fail with unsupported encoding and/or would return empty buffer. Example of column that returns empty buffer:
Patch removes
seen_num_values
increment for dictionary pages, because they are usually followed by data page that contains "values"/indices. Also fixed encoding reassignment.Updated unittest to reflect these changes + tested manually.
Fixes #10.