Skip to content

DB based configstore causes issues with advanced visibility #7558

@Ramkumar92

Description

@Ramkumar92

Version of Cadence server, and client(which language)

  • Server version: 1.3.6
  • Client version: 4.0.0
  • Client langauge: Java

Describe the bug
DB based configstore causes issues with advanced visibility, it doesn't appear to work when there are multiple attributes in frontend.validSearchAttributes

To Reproduce
Is the issue reproducible?

  • Yes

Steps to reproduce the behavior:

  1. Enable the db based configstore dynamicconfig with the following configuration:
dynamicconfig:
  client: configstore
  configstore:
    pollInterval: "10s"
    updateRetryAttempts: 20
    FetchTimeout: "2s"
    UpdateTimeout: "2s"
  1. Update the dynamicconfig values incl frontend.validSearchAttributes using cadence CLI & verified the updates are reflected by querying the dynamicconfig values using cadence CLI.
  2. Access the WEB UI we get the following error
    {
    "message": "invalid search attribute "StartTime"",
    "cause": {
    "grpcStatusCode": 3,
    "httpStatusCode": 400,
    "name": "GRPCError"
    }
    }

Expected behavior
Search attributes should work correctly with configstore similar to filebased dynamicconfig

Screenshots
Image

CC: @demirkayaender @davidporter-id-au

Metadata

Metadata

Assignees

No one assigned

    Labels

    up-for-grabsIssues that are good entry points for those new to Cadence that want to contribute

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions