feat: implement filter in cdc and incremental#756
Merged
Conversation
…eat/filter-in-cdc&incremental
…eat/filter-in-cdc&incremental
…eat/filter-in-cdc&incremental
b75a508 to
ab0848f
Compare
…eat/filter-in-cdc&incremental
…eat/filter-in-cdc&incremental
…eat/filter-in-cdc&incremental
vishalm0509
reviewed
Mar 13, 2026
…eat/filter-in-cdc&incremental
vishalm0509
previously approved these changes
Mar 16, 2026
…atazip-inc/olake into feat/filter-in-cdc&incremental
vaibhav-datazip
approved these changes
Mar 18, 2026
vishalm0509
approved these changes
Mar 20, 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
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
This PR adds filtering capability for CDC and incremental sync modes, allowing users to selectively sync records based on configurable filter conditions.
Fixes # (issue)
Type of change
=,!=,<,>,<=,>=How Has This Been Tested?
Comprehensive test coverage in
destination/filter_test.goincluding:Legacy filter support
Multiple operators and data types
AND/OR logic
Null value handling
Type coercion
Edge cases
Scenario A
Scenario B
Screenshots or Recordings
Documentation
Related PR's (If Any):
New Filter Format
Filters can be specified in the stream configuration using the new
FilterInputstructure:{ "selected_streams": { "namespace": [ { "stream_name": "table_1", "filter_input": { "logical_operator": "AND", "conditions": [ { "column": "id", "operator": ">", "value": 100 }, { "column": "status", "operator": "=", "value": "active" } ] } } ] } }Legacy Filter Format (Still Supported)
The legacy string-based filter format continues to work:
{ "filter": "id > 100 AND status = \"active\"" }