Fix failed search-index variants because of cluster name conflict

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Unknown
    • 3.8.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Fully Compatible
    • Dotnet Drivers
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      If we run more that one search-index in parallel (when multiple commits got to the main in relatively the same time, or if we run search-index variants at custom patch) that variant could fail with the following error message:

      Cluster name dbx-csharp-search-index-5843579d8414371e cannot have same first 23 characters as another cluster or serverless instance name in same group.

      We need to adjust cluster prefix to avoid such errors.

            Assignee:
            Oleksandr Poliakov
            Reporter:
            Oleksandr Poliakov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: