Support for databricks JSON path syntax #35
Merged
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
deifactor
force-pushed
the
ash/databricks-colon
branch
from
a763cb4 to
5c80a72
Compare
jmhain
approved these changes
Jun 13, 2025
deifactor
force-pushed
the
ash/databricks-colon
branch
from
7cf6ee0 to
fa4dd4d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
dbx uses
foo:bar.baz, like snowflake, but importantly requires the colon even when using square brackets.I didn't add support for backtick-escaped path identifiers like
foo:\bar`` because the customer isn't running into it yet so it can wait.