Skip to content
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

Regression: namespace specific search attributes have registration delay with system.forceSearchAttributesCacheRefreshOnRead=true #4017

Closed
bergundy opened this issue Mar 6, 2023 · 0 comments
Assignees

Comments

@bergundy
Copy link
Member

bergundy commented Mar 6, 2023

Expected Behavior

Starting a workflow immediately after registering a search attribute should succeed.

Actual Behavior

Starting a workflow immediately after registering a search attribute fails with:

INVALID_ARGUMENT: Namespace default has no mapping defined for search attribute foo

Steps to Reproduce the Problem

  1. Start Temporal server with SQLite (or any other SQL backend), for convenience use the Debug Server with SQLite VS Code launch config.
  2. Register a namespace: temporal operator namespace create default
  3. Use a client to add a search attribute
  4. Start a workflow with the added search attribute
  5. Observe the INVALID_ARGUMENT error

TypeScript snippet:

  await connection.operatorService.addSearchAttributes({
    namespace: 'default',
    searchAttributes: { foo: temporal.api.enums.v1.IndexedValueType.INDEXED_VALUE_TYPE_KEYWORD },
  });
  const client = new Client({ connection });
  const result = await client.workflow.execute(workflowType, {
    workflowId,
    taskQueue: 'test',
    args,
    searchAttributes: { foo: ['bar'] },
  });

Specifications

  • Version: latest master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants