add context flag "useAutoColumnSchemas" to use new auto types for MSQ segment generation #14175
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.
Description
Adds new MSQ query context parameter
useAutoColumnSchemas
as a sort of hacky backdoor to allow using the latest and greatest features added in #14014 and related PRs (#13803, etc). When set, all columns except for customCOMPLEX
column types will use the native 'auto' column indexer added in #14014 when generating segments. I call this a bit hacky because MSQ doesn't officially support the true array types besidesARRAY<STRING>
, which is translated intoSTRING
unless the new context flag is set, but other array types can be still be ingested by specifyingCOMPLEX<json>
as the input schema to use the complex passthrough.I did not document this at this time on purpose, this is mainly for allowing experimentation with the newer column features and MSQ.
This PR has: