# Different Query Returns for Kibana and FME HTTP Caller

**URL:** <https://discuss.elastic.co/t/different-query-returns-for-kibana-and-fme-http-caller/242926>\
**Category:** Elasticsearch\
**Created:** [July 28, 2020, 3:23pm UTC](https://discuss.elastic.co/t/different-query-returns-for-kibana-and-fme-http-caller/242926 "2020-07-28T15:23:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jattoe](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@jattoe](https://discuss.elastic.co/u/jattoe)\
**Post date:** [July 28, 2020, 3:23pm UTC](https://discuss.elastic.co/t/different-query-returns-for-kibana-and-fme-http-caller/242926/1 "2020-07-28T15:23:49Z")

</div>

I have been using the dev tools console on Kibana to write my queries and make sure everything is working as I would like. You can see an example of the return I get below.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/2/32a491cc7a927263cd5741b8faaf5aada6356f5c.png)

I then take this query and put it into an http caller in FME 2019.2.1 which yields the results shown in the second photo.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/b/1bdcfc5ab9c10bfba872a02490d8724b6f4a1be2.png)

Can anyone help me figure out why the DECK\_BODY field is displayed as one line with the line breaks shown as \n?  
Here is the query being used:

```
GET gffp_filings/_search?size=1&pretty=true
{
  "query": {
    "bool": {
      "must": [
           {
             "match": {
               "ACCESSION_NUMBER.keyword": "0000079879-20-000044"
             }
           },
           {
             "match": {
               "CIK_OR_ID.keyword": "0000079879"
             }
}]
}},
  "_source": ["DECK_BODY"]
}

```

Thanks for any help you can provide.

---

<div class="post-metadata">

**Author:** ![kelk](https://avatars.discourse-cdn.com/v4/letter/k/13edae/32.png) [@kelk](https://discuss.elastic.co/u/kelk)\
**Post date:** [July 28, 2020, 3:26pm UTC](https://discuss.elastic.co/t/different-query-returns-for-kibana-and-fme-http-caller/242926/2 "2020-07-28T15:26:20Z")

</div>

Kibana is just trying to make it friendlier to you by making (`\n` ) as new-line character. if you use curl or similar tools you get `\n` and to me both looks similar

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 25, 2020, 3:26pm UTC](https://discuss.elastic.co/t/different-query-returns-for-kibana-and-fme-http-caller/242926/3 "2020-08-25T15:26:22Z")

</div>

Closed on August 25, 2020, 3:26pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.