Skip to content

Conversation

@awln-temporal
Copy link
Contributor

@awln-temporal awln-temporal commented Nov 13, 2025

Add search attribute alias to field mapping to Namespace Detail for ElasticSearch.

  • TODO: Run test cluster and register search attributes via Operator APIs
  • TODO: Resolve potential mismatched custom mappers
  • TODO: Add query converter interceptors of aliased values for ES Visibility Queries.

Why?

Currently, when a Cluster is configured with ElasticSearch, search attribute registration via the Operator API AddSearchAttributes persist the user aliased search attributes in the ClusterMetadata without writing to the Namespace Detail.

ClusterMetadata is meant to list all pre-allocated custom search attribute column names and their types.

Search attributes are namespace scoped, registering at the ClusterMetadata level leads unexpected behavior.

What changed?

To support backwards compatibility with existing Clusters, existing search attributes in the ClusterMetadata must be replicated to each NamespaceDetail at startup.

All pre-allocated fields must be added to the ClusterMetadata, similar to existing SQL implementations.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)

@awln-temporal awln-temporal requested review from a team as code owners November 13, 2025 20:12
@awln-temporal awln-temporal force-pushed the esAliasMappingRegistration branch from 0df71f0 to 5a9dc24 Compare November 13, 2025 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants