Skip to content

feat: 支持surrealDB图关联查询 --story=133245352 - #1433

Open
Zhaoyikaiii wants to merge 24 commits into
TencentBlueKing:masterfrom
Zhaoyikaiii:feat/surrpot_v1beta3_surrealDB_query/1010158081133245352
Open

feat: 支持surrealDB图关联查询 --story=133245352#1433
Zhaoyikaiii wants to merge 24 commits into
TencentBlueKing:masterfrom
Zhaoyikaiii:feat/surrpot_v1beta3_surrealDB_query/1010158081133245352

Conversation

@Zhaoyikaiii

Copy link
Copy Markdown
Collaborator

支持 surrealDB v1beta3 图关联查询。

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 42d6e666a5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +156 to +159
if resourceType == source || resourceType == target {
// 调用方有时会把完整资源路径原样传回来,例如 [source, ..., target]。
// 路径搜索本身已经固定两端点,这里只保留中间资源约束,避免把端点重复参与连续片段判断。
continue

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve endpoint anchoring in path_resource constraints

When a caller passes a partial or full path_resource that includes an endpoint, these lines drop every occurrence of the source/target before the contiguous-path check. For example, a constraint like [source, b, target] becomes just [b], so paths with extra hops such as source -> a -> b -> c -> target are accepted even though the caller pinned a specific contiguous route. This can make the new v1beta3 API return targets through a path the request explicitly tried to exclude.

Useful? React with 👍 / 👎.

Comment on lines +485 to +487
if err := validateTargetCount(len(matchers)); err != nil {
span.Set("failure-stage", "target-limit")
return nil, nil, nil, err

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Skip whole-interval target limits for range queries

This validation runs for both instant and range modes, but in range mode matchers is the distinct target set across the whole interval, not the per-timestamp result that the range API later returns and validates with validateRangeTargetCounts. A range query where each bucket stays under MaxTargets but the union across all buckets exceeds it will be rejected as truncated/400 before the per-bucket limit check can run.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant