Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Columnar table schemas currently show compression without indicating dictionary encoding. Add an Encoding column to the schema sidebar and Diagnostics → Schema, with a Dictionary label for enabled columns and sorting that brings them first.
Recognize both
DataAccessorConstructor.ClassName = "DICTIONARY"and legacyDictionaryEncoding.Enabled, giving the current accessor precedence. Missing, disabled, and unknown settings remain unmarked. The label reflects the configured schema encoding.Validation on the PR branch:
npm run typecheck,npm run lint(existing warnings only),npm test -- --runInBand(237 suites / 2,182 tests),npm run build:embedded, andnpm run packagepassed.Screenshot with demo schema data:
Full-size screenshot (Yandex internal)