Skip to content

Conversation

@vishwarajanand
Copy link
Contributor

Per this comment, separating out the code changes for numpy #V2.

This change is needed because when using numpy V2, if a numpy array is converted to string then it comes as numpy objects rather than float array. ref

Changes include:

  1. Parsing embedding dimensions individually for accommodating numpy V2 values.
  2. Updating tests accordingly.

@product-auto-label product-auto-label bot added the api: cloudsql-postgres Issues related to the googleapis/langchain-google-cloud-sql-pg-python API. label Mar 3, 2025
@vishwarajanand vishwarajanand marked this pull request as ready for review March 3, 2025 14:52
@vishwarajanand vishwarajanand requested review from a team as code owners March 3, 2025 14:52
@vishwarajanand vishwarajanand mentioned this pull request Mar 3, 2025
Copy link
Collaborator

@averikitsch averikitsch left a comment

Choose a reason for hiding this comment

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

Can you update the commit message to use "refactor:"?

Thank you @vishwarajanand !

@vishwarajanand vishwarajanand changed the title fix: parse embedding dimensions as float[] for numpyV2 refactor: parse embedding dimensions as float[] for numpyV2 Mar 4, 2025
@vishwarajanand vishwarajanand merged commit ed1c9fd into main Mar 4, 2025
11 checks passed
@vishwarajanand vishwarajanand deleted the numpyV2-code-changes branch March 4, 2025 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: cloudsql-postgres Issues related to the googleapis/langchain-google-cloud-sql-pg-python API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants