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

Find a way not to have a configuration or hard-code the list of indexes in validate or harvest, so to check products across nodes #1116

Open
tloubrieu-jpl opened this issue Jan 23, 2025 · 2 comments

Comments

@tloubrieu-jpl
Copy link
Member

💡 Description

Use alias or index pattern, ...

As a start see https://chatgpt.com/share/6792c900-c964-8008-bac5-97710fc3344e

⚔️ Parent Epic / Related Tickets

No response

@tloubrieu-jpl
Copy link
Member Author

We can have opensearch index alias on multiple indexes using a wildcard pattern.

See for example:

POST _aliases
{
  "actions": [
    {
      "add": {
        "index": "*-registry",
        "alias": "all-registry"
      }
    }
  ]
}

See documentation https://opensearch.org/docs/latest/im-plugin/index-alias/

This has been tested in dev opensearch serverless. As a validation, the count of the document in the alias is equal to the sum of the count for each aliased index.

We would not be able to write on this index, which makes sense but I did not test it , see https://stackoverflow.com/questions/19661822/is-it-possible-to-write-to-multiple-indexes-with-an-elasticsearch-alias

@al-niessner
Copy link
Contributor

@tloubrieu-jpl

If you packaged the configurations in registry-common so that everyone got them with them with the jar files, then you would not have to have magic lists of nodes embedded everywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ToDo
Development

No branches or pull requests

2 participants