[ENH] Export schema and search types from chromadb.api

[jairad26]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • This PR adds support for importing all search and schema related types from chromadb.api for simplified usage
• New functionality
  • ...

Test plan

How are these changes tested?
manually

• [ x] 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?

[jairad26]

• [ENH] Export schema and search types from chromadb.api #5736 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

Expose search & schema symbols through chromadb.api namespace

Streamlines end-user imports by re-exporting all schema-related types from chromadb.api.types and most search expression helpers from chromadb.execution.expression. A small alias (SearchWhere) was introduced and included in __all__ to clarify semantics. No functional logic was modified; changes are limited to import/export wiring.

Key Changes

• Prepended chromadb/api/__init__.py with wildcard import of chromadb.api.types and an explicit re-export list from chromadb.execution.expression (e.g., Search, Eq, Knn, etc.)
• Removed redundant import chromadb.execution.expression.plan.Search that is now covered by the new bulk import
• Added alias SearchWhere = Where in chromadb/execution/expression/__init__.py and exposed it via __all__

Affected Areas

• chromadb/api/__init__.py public API surface
• chromadb/execution/expression/__init__.py symbol table

This summary was automatically generated by @propel-code-bot

[propel-code-bot]

[BestPractice]

By exposing many new symbols through the chromadb.api namespace, it's important to clearly define the module's public API. Adding an __all__ variable will make it explicit which names are intended for export and will prevent leaking internal symbols (like ABC, override, Component, etc.) when users perform a wildcard import (from chromadb.api import *).

Context for Agents

[**BestPractice**]

By exposing many new symbols through the `chromadb.api` namespace, it's important to clearly define the module's public API. Adding an `__all__` variable will make it explicit which names are intended for export and will prevent leaking internal symbols (like `ABC`, `override`, `Component`, etc.) when users perform a wildcard import (`from chromadb.api import *`).

File: chromadb/api/__init__.py
Line: 37

[propel-code-bot]

[BestPractice]

The alias SearchWhere = Where creates a duplicate name that adds no functional value and may confuse users about which one to use. Since both SearchWhere and Where are exported in __all__, users will see both options without clear guidance on when to use each. Consider removing the alias and keeping only Where, or if the alias serves a specific backward compatibility purpose, document it with a comment explaining when to use each.

Context for Agents

[**BestPractice**]

The alias `SearchWhere = Where` creates a duplicate name that adds no functional value and may confuse users about which one to use. Since both `SearchWhere` and `Where` are exported in `__all__`, users will see both options without clear guidance on when to use each. Consider removing the alias and keeping only `Where`, or if the alias serves a specific backward compatibility purpose, document it with a comment explaining when to use each.

File: chromadb/execution/expression/__init__.py
Line: 48