Repository navigation
DuckDB Compatibility - #160
Merged
Merged
Conversation
* postgres-container-ci * add duckdb tests * fixes
…etran_utils into feature/duck-db
fivetran-jamie
commented
Aug 11, 2026
fivetran-jamie
commented
Aug 11, 2026
fivetran-jamie
marked this pull request as ready for review
August 11, 2026 19:24
fivetran-jamie
commented
Aug 11, 2026
fivetran-jamie
commented
Aug 11, 2026
fivetran-catfritz
approved these changes
Aug 12, 2026
fivetran-catfritz
left a comment
fivetran-catfritz
left a comment
Contributor
There was a problem hiding this comment.
A few suggestions but nothing stopping approval!
fivetran-joemarkiewicz
requested changes
Aug 12, 2026
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
fivetran-joemarkiewicz
approved these changes
Aug 12, 2026
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
3 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.
What change does this PR introduce?
DuckDB Compatibility
If this PR introduces a new macro, how did you test the new macro?
Buildkite and running locally / confirming in DBeaver (confirmed json_parse produces non-null results)
If this PR introduces a modification to an existing macro, which packages is the macro currently present in and what steps were taken to test compatibility across packages?
Affected packages (that actually use the macros) with their accompanying PRs:
Qualtrics - timestamp diff
Jira - percentile
Zendesk - timestamp add
Intercom - percentile
Youtube - json parse
Shopify - json parse
Klaviyo - json_parse
Did you update the README to reflect the macro addition/modifications?