fix(vikingdb): normalize created_at filters in API key client - #3954
Open
heaoxiang-ai wants to merge 2 commits into
Open
fix(vikingdb): normalize created_at filters in API key client#3954heaoxiang-ai wants to merge 2 commits into
heaoxiang-ai wants to merge 2 commits into
Conversation
heaoxiang-ai
force-pushed
the
fix/time-range-filter-serialization
branch
from
August 12, 2026 08:21
cc17b36 to
a3da8f6
Compare
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
Fix date filtering for the commercial VikingDB data plane that uses Bearer API-key authentication. OpenViking keeps compiling
TimeRangeto its existing internalrangeDSL, whileVolcengineApiKeyCollectionnow translates onlycreated_atrange nodes inside the outgoingfilterto VikingDBtime_rangenodes.This keeps the shared adapter behavior unchanged for local, cuVS, HTTP, Volcengine AK/SK, and custom backends.
Human Involvement
Related Issue
N/A
Type of Change
Changes Made
rangetotime_rangeonly forcreated_atnodes in the outgoing VikingDB API-key client filter.filter; upsert and update data remain untouched.rangenodes and nested boolean filter structure.Testing
Verified by directly invoking the focused client test with
uv run python; the API-key client test passed, and an additional assertion confirmed the shared base adapter still emitsrange.Also verified:
Checklist
Screenshots (if applicable)
N/A
Additional Notes
The local full pytest invocation exits with status 139 while loading the native-extension test environment. The focused client test itself passes when invoked directly.