Display user-specified operator in ParquetTable example docs_filters#50
Draft
amoonrat wants to merge 4 commits intoneuralinkcorp:mainfrom
Draft
Display user-specified operator in ParquetTable example docs_filters#50amoonrat wants to merge 4 commits intoneuralinkcorp:mainfrom
amoonrat wants to merge 4 commits intoneuralinkcorp:mainfrom
Conversation
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
1 participant
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.
When declaring ParquetTables, a filter could be passed into
docs_filterswith an operator other than"=", such as"contains". However, the user-specified operator isn't passed through to the generated code examples on the static site, which hardcodes filters to display operator"=", creating confusion for users of the web catalog trying to properly query the data.This passes the user-specified operator from table declaration through to the static site codegen.