Troubleshooting an OpenSearch index with an ID containing non-ASCII characters
If you create an OpenSearch index whose ID contains non-ASCII characters, you may run into problems passing that ID to a Powershell script. One solution is to exclusively use OpenSearch indexes that contain only ASCII characters. The other solution is to change your regional settings.
Before you begin
About this task
- You have successfully created an OpenSearch index and given it an ID containing Japanese characters, for example,
コネクター. - You now want to remove this index using the ManageElasticsearchIndex.ps1 script.
- The JSON output being added to OpenSearch contains numerous
????strings, whereコネクターwas expected.
The cause of the problem is the Japanese string, which is being passed as a Windows environment variable value. On a Windows instance that is not configured to accept non-ASCII values, the Japanese string is rendered as ????.