Skip to content

Support Aliyun Elasticsearch query encoding - #835

Draft
vicety wants to merge 1 commit into
zilliztech:mainfrom
vicety:agent/aliyun-elasticsearch-query-encoding
Draft

Support Aliyun Elasticsearch query encoding#835
vicety wants to merge 1 commit into
zilliztech:mainfrom
vicety:agent/aliyun-elasticsearch-query-encoding

Conversation

@vicety

@vicety vicety commented Aug 5, 2026

Copy link
Copy Markdown

What changed

  • Allow the Aliyun Elasticsearch index name and ID field to be overridden with VDBBENCH_ALIYUN_ES_INDEX and VDBBENCH_ALIYUN_ES_ID_FIELD.
  • Encode query vectors as big-endian float32 bytes and Base64 before delegating to the Elastic Cloud search implementation.

Why

Aliyun Elasticsearch expects the query vector in its binary Base64 representation, and deployments may use custom index and ID field names.

Validation

The implementation was manually validated by the contributor.

@sre-ci-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vicety
To complete the pull request process, please assign xuanyang-cn after the PR has been reviewed.
You can assign the PR to them by writing /assign @xuanyang-cn in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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.

2 participants