Skip to content

Add support for elastic embedding sizes under 768 dimensions #402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

demoncoder-crypto
Copy link

Add support for elastic embedding sizes under the standard 768 dimensions

Description

This PR adds support for customizing embedding dimensions in text embedding models, similar to what's available in the Python API. Users can now request embeddings with dimensions of 128, 256, 384, 512, or 768 (default).

Changes

  • Added dimensions parameter to EmbedContentRequest interface
  • Updated formatEmbedContentInput to validate dimension values
  • Added sample code demonstrating how to use elastic embedding sizes
  • Updated README with documentation and examples
  • Added unit tests for the new functionality

Testing

The implementation includes validation to ensure only supported dimension values (128, 256, 384, 512, 768) are used. The code has been successfully built and tested locally.

Copy link

google-cla bot commented Mar 8, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@Annhiluc Annhiluc added type:feature request New feature request/enhancement status:triaged Issue/PR triaged to the corresponding sub-team p3 labels Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p3 status:triaged Issue/PR triaged to the corresponding sub-team type:feature request New feature request/enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants