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

Creating an index with the name "." causes strange behavior #2326

Closed
lukasolson opened this issue Dec 15, 2014 · 3 comments · Fixed by #2381
Closed

Creating an index with the name "." causes strange behavior #2326

lukasolson opened this issue Dec 15, 2014 · 3 comments · Fixed by #2381
Assignees
Labels
bug Fixes for quality problems that affect the customer experience PR sent
Milestone

Comments

@lukasolson
Copy link
Member

When you create a new index pattern of . (just a single period), when it saves, it saves it with a really funky name.

2014-12-15 14_50_23

@lukasolson lukasolson added the bug Fixes for quality problems that affect the customer experience label Dec 15, 2014
@lukasolson lukasolson added this to the 4.0.0-RC1 milestone Dec 15, 2014
@lukasolson lukasolson self-assigned this Dec 16, 2014
@lukasolson
Copy link
Member Author

It turns out that this is a bug with Elasticsearch's JS library. When you send a request to get the mapping for ".", it returns all mappings instead of giving some sort of error, and then when you create the index with "." in the URL, it is ignored and a document is inserted with a generated ID.

@lukasolson
Copy link
Member Author

Also, see elastic/elasticsearch#6736.

@lukasolson lukasolson reopened this Dec 16, 2014
@lukasolson
Copy link
Member Author

So after talking about this, we decided it would be best to create some sort of validation on the client to prevent invalid index name patterns from being created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience PR sent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant