ElasticSearch error while sending data

Question

I am trying to send a JSON to elasticSearch. I have tried using Postman and SOAPUI The data is

[{"column1": "abc", "column2": "def", "column3": "dghi", "column4": "jkl", "column5": "mno"}, {"column1": "pqr", "column2": "stu", "column3": "vwx", "column4": "", "column5": ""}]

I am getting the following error back

{
  "error": {
    "root_cause": [
      {
        "type": "mapper_parsing_exception",
        "reason": "failed to parse"
      }
    ],
    "type": "mapper_parsing_exception",
    "reason": "failed to parse",
    "caused_by": {
      "type": "not_x_content_exception",
      "reason": "Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes"
    }
  },
  "status": 400
}

But when I post a single JSON array I.e.

{"column1": "abc", "column2": "def", "column3": "dghi", "column4": "jkl", "column5": "mno"}

Then it works fine. I am new to ElasticSearch so not sure what is going wrong.

Jay Stevens · Accepted Answer · 2018-10-02 21:41:16Z

14

Try using curly brackets first, then naming the array. Try that and see if it works.

For example:

{root:[1, 2, 3, 4, 5]}

might work because it's contained inside an object.

Even better; while I was experimenting with JSON.stringify();, I found that it coverts arrays to JSON like so:

{1, 2, 3, 4, 5}

edited Oct 2, 2018 at 21:41

Jay Stevens

5,9239 gold badges46 silver badges68 bronze badges

answered Feb 4, 2016 at 23:21

hellol11

4284 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Samuel Neff Over a year ago

-1, While this is leading toward the correct answer, it's not really explanatory and the negative tone is really not helpful. The original question does have valid JSON, it's a single-element array. The issue that this question answers is that ElasticSearch requires the outermost document to be a JSON object, not a JSON array or scalar value. Example refactoring would be good too and not take too long in this case.

Brandon Kearby · Accepted Answer · 2018-02-08 14:35:08Z

12

I recently ran into this using curl and it was a simple typo. I was not using inline json, but from a file. I forgot to include the @ sign before the filename.

curl -XPUT -H'Content-Type:application/json' localhost:9200/twitter [email protected]

answered Feb 8, 2018 at 14:35

Brandon Kearby

6037 silver badges8 bronze badges

Comments

noobEngineer · Accepted Answer · 2016-02-06 18:17:08Z

8

thanks @hellol11

it worked when I changed to

    {root :
[
    {"column1": "abc", "column2": "def", "column3": "dghi", "column4": "jkl", "column5": "mno"},
    {"column1": "pqr", "column2": "stu", "column3": "vwx", "column4": "", "column5": ""}

]}

answered Feb 6, 2016 at 18:17

noobEngineer

3831 gold badge2 silver badges8 bronze badges

1 Comment

Nguai al Over a year ago

don't you need quotes around root?

Scott Nestor · Accepted Answer · 2018-10-27 22:13:24Z

5

I had this issue inside a Python script (using requests) to try and POST to ES. The resolution was simply to convert the json object to a string using json.dumps()

Example (Python snipit):

import json
import requests

headers={'Content-Type': 'application/json'}
data={'hello':'barney'} 

response = requests.post('https://<my_es_domain>/<my_es_ix>/<my_doc_type>', data=json.dumps(data), headers=headers)

answered Oct 27, 2018 at 22:13

Scott Nestor

511 silver badge1 bronze badge

Comments

Ahmed Ashour · Accepted Answer · 2017-04-14 05:07:48Z

4

In Windows environment, I solved this problem.

-d plus double quotation(")

and surround name with backslash plus double quotaton(\")

command>

curl (more-option) -d "{\"column1\": \"abc\", \"column2\": \"def\", \"column3\": \"dghi\", \"column4\": \"jkl\", \"column5\": \"mno\"}"

edited Apr 14, 2017 at 5:07

Ahmed Ashour

5,66310 gold badges41 silver badges63 bronze badges

answered Apr 14, 2017 at 4:40

Jung

663 bronze badges

Comments

raviabhiram · Accepted Answer · 2019-06-07 18:23:06Z

1

I was getting the same error while trying to post to elasticsearch but using node js. I used the node-fetch package to make a PUT request to elasticsearch. It was weird because using the exact same thing on postman I got no error but I was getting the error on node js. I was initially doing:

const current = {
    "id" : "123456789"
}
const options = {
    method: "POST",
    headers: {
        "Content-Type": "application/json"
    },
    body: current
}

Turns out the error got fixed when I changed it to:

body: JSON.stringify(current)

answered Jun 7, 2019 at 18:23

raviabhiram

7302 gold badges9 silver badges23 bronze badges

Comments

Bowrna · Accepted Answer · 2022-12-09 08:29:03Z

1

I faced similar issue when sending JSON to Elasticsearch using Python requests. This is the code snippet that caused issue. I didn't have any issue with json_docs json. It was a simple JSON object. But passing the json_docs as json param caused issue.

def dump_to_es(es_path, json_docs):
    headers = {
        'Content-Type': 'application/json',
    }   
    response = requests.put(f"http://localhost:4171/{es_path}", headers=headers, json=json_docs)
    print(f"Elasticsearch response for {es_path}:", response.text)

When passed the json_docs as data param it works without issue.

response = requests.put(f"http://localhost:4171/{es_path}", headers=headers, data=json_docs)

edited Dec 9, 2022 at 8:29

answered Dec 9, 2022 at 8:23

Bowrna

1411 silver badge6 bronze badges

2 Comments

Andrew Grasso Over a year ago

Same thing for me, your solution does indeed work. I would like to know why using the json option in requests causes this.

Bowrna Over a year ago

check the response in this link: stackoverflow.com/questions/26685248/…. As mentioned by this user @michael-ekoka, that value passed on to the json parameter is double encoded. You can also check the following code in github to see where parameter passed to json passes through json.dumps (github.com/kennethreitz/requests/blob/…)

balram pundir · Accepted Answer · 2017-08-23 19:05:08Z

0

In elastic search ,if you want to post bulk data then each list object must be in New line .so if you are using sense then make everything in New line or if using from code then add New line character \n...

answered Aug 23, 2017 at 19:05

balram pundir

1

Comments

Raphaël Goisque · Accepted Answer · 2022-11-20 17:40:05Z

0

For those who directly want to send data in the curl query and get the "not_x_content_exception" error, I've Managed to fix it by using double quotes:

curl -X POST "http://localhost:9200/my_index/_doc/1" -H "Content-Type: application/json" -d "{ ""name"": ""Paul"" }"

edited Nov 20, 2022 at 17:40

answered Jul 6, 2022 at 9:04

Raphaël Goisque

6631 gold badge8 silver badges11 bronze badges

Collectives™ on Stack Overflow

ElasticSearch error while sending data

9 Answers 9

1 Comment

Comments

1 Comment

Comments

Comments

Comments

2 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

9 Answers 9

1 Comment

Comments

1 Comment

Comments

Comments

Comments

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related