feat: add is_case_insensitive #391
Open
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
nguymin4
requested review from
ayushmjain,
bradmiro,
davenportjw,
q2w and
a team
as code owners
nguymin4
force-pushed
the
nguymin4/is-case-insensitive
branch
from
6bf3478 to
693442d
Compare
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.
This PR adds
is_case_insensitivevariable as optionalis_case_insensitive - - (Optional) TRUE if the dataset and its table names are case-insensitive, otherwise FALSE. By default, this is FALSE, which means the dataset and its table names are case-sensitive. This field does not affect routine references.
Note:
make generate_docsas instructed in contributing guidelines. It created unrelated changes, e.g. it convertedconfigurationSecsfrom integer to string (???) inmodules/data_warehouse/metadata.yaml.=> Therefore, I only committed what make senses.