Different Query Returns for Kibana and FME HTTP Caller

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.

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.

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.

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

1 Like

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