Is this page helpful?

Release Notes#

Current Release#

USD Search API 1.3.1#

Release Date: May 2026

  • Helm chart documentation improvements, rendering service improvements, and bug fixes

Added#

  • Configurable OpenSearch serializer via global.search_backend_config.serializer setting (default: orjson)

  • Search REST API HPA autoscaler

  • Documentation on using rendering service as an alternative to rendering jobs

  • Thumbnail indexing settings configuration documentation

  • Maintenance mode for deploying the helm chart without background indexing (for Redis queue cleanup and other database maintenance)

  • rendering-service.settings.load_asset_as_reference — USD assets with a default prim are referenced into the scene rather than opened as a sublayer; falls back to sublayer when no default prim is defined. Available for both the rendering service and Kubernetes rendering job.

  • Configurable rendering-service.settings.kit_extra_args and rendering-service.loggingConfig from the main chart values.yaml

  • Search Backend Readiness Init Container — added to all services that depend on OpenSearch, ensuring the backend is ready before dependent containers start

Fixed#

  • Query Results Validation with Image Prompt — query results validation was not working properly with an image prompt

  • Rendering Service Ephemeral Storage Exhaustion — rendering service was writing cache to an internal location, causing ephemeral storage to be overloaded and containers to be evicted

Updated#

  • Default settings for the rendering service temporary directory

  • API gateway configuration to expose the search validation endpoint

Removed#

  • Memcached dependency — no caching performance improvement observed for rendering jobs and rendering service

  • Deprecated storage service interface for OpenSearch backend

Known Limitations#

  • USD Search API relies on Omniverse Kit for rendering and extracting scene prim hierarchy. Therefore the service should work with any scene that Omniverse Kit can work with.

  • When using the filter_by_properties query parameter in USD Search API, different filters must be separated by a single comma (having a comma and a space is not supported).

  • Pagination of search results is currently not supported.

All Releases#