-
Notifications
You must be signed in to change notification settings - Fork 917
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
[BUG] Can't create index pattern with special characters #877
Comments
@jere-ortega24 with your OpenSearch version, I assume you mean the open source OpenSearch version 1.0.0 and not anything specific to the AWS managed service? Just wanted to validate. Assuming the former, can we pull "provided by AWS"? |
@ahopp done |
Hello @jere-ortega24, thanks for opening this. How did you create your index pattern? And was able to create an index pattern: I currently used the |
I am trying to reproduce this issue and verify ur solution. I follow the same thing on v1.1 but I couldn't reproduce it. Seems work for me. |
I would like to add that all of the "Index Management" app - index filters are affected by something similar. How to reproduce:
Sure I can type other things, but '.ds' should work. Also hypen '-' will clear all results too. Hopefully this helps / Creates more work :-) |
Hey @camAtGitHub , we don't have 'Managed indicies' in the dashboards now. We only have index pattern. Can we help us understand ur question? |
@ananzh Opensearch Plugins > Index Management > Managed Indices. Is the general location I was referring to. Most, if not all of the search-index-filters-thingy-ma-bobs under 'Index Management' (plugin?) are affected by my previous comment. |
I created it using logstash 7.13.2 from the public docker image which has installed the output plugin 1.0.0. But checked right now creating it from the dev tools and is the same behavior. @ananzh It might have been already fixed in 1.1 then. I will check. @camAtGitHub i think you meant Policy managed indices. And yes i can confirm that it doesn't work for me either. Using |
FYI I'm on 1.1 docker edition and it's broken here too |
Ok I have checked and you are right it has been fixed in 1.1. @camAtGitHub I checked and yes it also happens in 1.1, but i think you should probably open an issue in opensearch-project/index-management-dashboards-plugin as I understand it that's where that issue is. I'm closing this issue, thanks for your help. |
# [24.1.0](elastic/elastic-charts@v24.0.0...v24.1.0) (2020-11-24) ### Bug Fixes * **area_charts:** correctly represent baseline with negative data points ([opensearch-project#896](elastic/elastic-charts#896)) ([b622fda](elastic/elastic-charts@b622fda)) * **legend:** legend sizes with ordinal data ([opensearch-project#867](elastic/elastic-charts#867)) ([74bcbad](elastic/elastic-charts@74bcbad)), closes [opensearch-project#811](elastic/elastic-charts#811) * render orphan data points on lines and areas ([opensearch-project#900](elastic/elastic-charts#900)) ([3e2c739](elastic/elastic-charts@3e2c739)), closes [opensearch-project#783](elastic/elastic-charts#783) * specs swaps correctly reflected in state ([opensearch-project#901](elastic/elastic-charts#901)) ([a94347f](elastic/elastic-charts@a94347f)) ### Features * **legend:** allow legend text to be copyable ([opensearch-project#877](elastic/elastic-charts#877)) ([21a96d3](elastic/elastic-charts@21a96d3)), closes [opensearch-project#710](elastic/elastic-charts#710) * allow clearing series colors from memory ([opensearch-project#899](elastic/elastic-charts#899)) ([e97f4ab](elastic/elastic-charts@e97f4ab)) * merge series domain with the domain of another group ([opensearch-project#912](elastic/elastic-charts#912)) ([716ad5a](elastic/elastic-charts@716ad5a)) * small multiples for XY charts (alpha) ([opensearch-project#793](elastic/elastic-charts#793)) ([3b88e1c](elastic/elastic-charts@3b88e1c)), closes [opensearch-project#500](elastic/elastic-charts#500) [opensearch-project#500](elastic/elastic-charts#500)
Describe the bug
When creating an index pattern with special character it doesn't find the existing indices and doesn't let you create the index pattern. If you encode the pattern for url, it finds the indices and lets you create the index pattern, but later gives errors because it doesn't find any indices that match.
To Reproduce
[my-app]-1
Stack Management > Index Patterns > Create index pattern
[my-app]-*
%5Bmy-app%5D-*
which is url encodedExpected behavior
It should find the matching indices using the pattern
[my-app]-*
, let you create the index pattern and find the fields.OpenSearch Version
1.0.0
Dashboards Version
1.0.0
Host/Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: