-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[BUG] is_default_schema does not do a space check for defaults or #embedding #5787
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
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
|
Fix The PR addresses an edge-case where Key Changes• Added Affected Areas• This summary was automatically generated by @propel-code-bot |
3df7c34 to
dea4481
Compare
dea4481 to
8ad206c
Compare
…bedding (#5787) ## Description of changes _Summarize the changes made by this PR._ - Improvements & Bug fixes - There is a bug in schema where is_default_schema does not check the space when confirming if the schema is default. This was hidden by our e2e tests, since we used an ef with a default space of cosine. therefore the configuration was cosine and was automatically converted into the schema and tests passed. this PR adds a new test to confirm the basic space setting scenario works - New functionality - ... ## Test plan _How are these changes tested?_ - [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust ## Migration plan _Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_ ## Observability plan _What is the plan to instrument and monitor this change?_ ## Documentation Changes _Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_
This PR cherry-picks the commit a22959d onto release/2025-10-24. If there are unresolved conflicts, please resolve them manually. Co-authored-by: Jai Radhakrishnan <[email protected]>
…bedding (#5787) ## Description of changes _Summarize the changes made by this PR._ - Improvements & Bug fixes - There is a bug in schema where is_default_schema does not check the space when confirming if the schema is default. This was hidden by our e2e tests, since we used an ef with a default space of cosine. therefore the configuration was cosine and was automatically converted into the schema and tests passed. this PR adds a new test to confirm the basic space setting scenario works - New functionality - ... ## Test plan _How are these changes tested?_ - [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust ## Migration plan _Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_ ## Observability plan _What is the plan to instrument and monitor this change?_ ## Documentation Changes _Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_
This PR cherry-picks the commit a22959d onto rc/2025-10-31. If there are unresolved conflicts, please resolve them manually. Co-authored-by: Jai Radhakrishnan <[email protected]>

Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rustMigration plan
Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?
Observability plan
What is the plan to instrument and monitor this change?
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?