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

Error handling on invalid mapping data #5864

Closed
ppf2 opened this issue Apr 18, 2014 · 0 comments
Closed

Error handling on invalid mapping data #5864

ppf2 opened this issue Apr 18, 2014 · 0 comments

Comments

@ppf2
Copy link
Member

ppf2 commented Apr 18, 2014

DELETE /test1
PUT /test1
PUT /test1/test/_mapping
{
  "mappings":
  {
    "test":{
      "properties":{
        "prop1":{
          "type": "string",
          "index" : "not_analyzed"
        }
      }
    }
  }
}
GET /test1/test/_mapping

The 2nd PUT request above is invalid but it is still accepted/acknowledged by the engine. Would be nice to add some validation to the above use case to return an error.

@brwe brwe self-assigned this May 8, 2014
brwe added a commit to brwe/elasticsearch that referenced this issue May 8, 2014
When a mapping is declared and the type is known from the uri
then the type can be skipped in the body (see elastic#4483). However,
there was no check if the given keys actually make a valid mapping.

closes elastic#5864
brwe added a commit to brwe/elasticsearch that referenced this issue May 10, 2014
When a mapping is declared and the type is known from the uri
then the type can be skipped in the body (see elastic#4483). However,
there was no check if the given keys actually make a valid mapping.

closes elastic#5864
brwe added a commit that referenced this issue May 12, 2014
When a mapping is declared and the type is known from the uri
then the type can be skipped in the body (see #4483). However,
there was no check if the given keys actually make a valid mapping.

closes #5864
closes #6093
@brwe brwe closed this as completed in 4b2e4be May 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants