You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 757f2ea
Browse filesBrowse the repository at this point in the historyBrowse files
// Cap keys per dispatched query: each key is another operation for the db to fetch, and simply fetching all keys at once can be too much for the db to handle.
80
80
exportconstGET_ALL_KEY_VALUES_CHUNK_SIZE=100;
81
81
82
-
// Distinct values a text index values lookup reads per key. The dictionary is
82
+
// Index rows a text index values lookup reads per key. The dictionary is
83
83
// sorted, so a key with more than this gets the most frequent among its
84
-
// alphabetically first ones. Keep it above "Load more"'s 10,000 values.
84
+
// alphabetically first ones.
85
85
constTEXT_INDEX_TOKENS_PER_KEY=20_000;
86
86
87
-
// mergeTreeTextIndex returns one row per part and token, so a value in every
88
-
// part read takes maxParts rows; scaling the LIMIT by maxParts keeps room for
89
-
// TEXT_INDEX_TOKENS_PER_KEY distinct values. A read of every part ("Load
90
-
// more") isn't capped.
87
+
// mergeTreeTextIndex returns one row per part and token, so the cap counts a
88
+
// value once per part it's in, and values only in parts read after it are
89
+
// missed. That sample is enough for the top values of a filter, but "Load
90
+
// more" (no part limit) wants every value, so its read isn't capped.
0 commit comments