-
Notifications
You must be signed in to change notification settings - Fork 58
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
[PROPOSAL] Discussion for the index name of AD Extension #241
Comments
Is there a way we can create a tool that users can use to migrate/rename their indices in bulk? |
I don't have much context for the extensions/sdk work but in OpenSearch currently |
@owaiskazi19 AD index
[1] https://opensearch.org/docs/latest/security-plugin/configuration/system-indices/ |
The problem @owaiskazi19 experienced in trying to create an detector with the
If there is already a system index permitted with this name, why are we receiving the |
TLDR: I will create a new bug on OpenSearch project to fix this, and then we can close this issue. |
Thanks @dbwiddis for explaining the issue with more details. @saratvemulapalli as @dbwiddis mentioned warning was not letting us populate the response object. Removing the |
I think the issue may be that plugins are disabled -- no security plugin which installs that index? |
Should we use opensearch.yml for extensions? I feel like we should keep it for old plugin architecture only. WDYT? |
Given that this is directly related to the security plugin configuration, we need to keep it where it is until security plugin features are migrated to core. @peternied may have insight on where these settings might live in the future. |
To keep moving fast, I'd recommend reusing the existing solution. The index protection features are not expected to see any updates in the planned future. To look forward, I think all extensions will want ways to persist data that is relevant to the OpenSearch cluster they are interacting with. While 'settings' can represent this, wouldn't it be a nice perk of interacting with OpenSearch that you could use it to store some of an extension's data in the common index format? Maybe extensions should get an index by default that they don't even need to think about the name of, it's provided automatically. What do folks think of making this a feature of extensions - @dbwiddis you think this is work opening an issue? |
What/Why
What are you proposing?
Currently, AD Extension creates a metedata index
As per 3.x version of OpenSearch only the system index should start with
.
. To resolve this warning we can change the name of the index toopensearch-anomaly-detectors
but this will break the backward compatibility.What problems are you trying to solve?
index name .opendistro-anomaly-detectors starts with a dot '.', in the next major version
Are there any breaking changes to the API
Backward compatibility needs to be handled with this new change of index name.
The text was updated successfully, but these errors were encountered: