Failed to CompressedXContent on RestHighLevelClient 7.13

Elastic Stack Elasticsearch
1

Hi,

I am getting the following exception when creatin new CompressedXContent for Template instance

ElasticsearchParseException[Failed to parse content to map]; nested: JsonParseException[Unexpected character ('p' (code 112)): was expecting double-quote to start field name
 at [Source: (byte[])"{properties={sessionId={type=keyword}, streamName={type=keyword}, _instance={type=long}, _update={type=date}, core={type=long}, episode={type=long}, fileIndex={type=long}, globalTimestamp={type=date}, id={type=keyword, index=false}, index={type=long}, name={type=keyword, normalizer=lowercase}, source={type=keyword}, subSource={type=keyword}, threadId={type=long}, timestamp={type=long}, type={type=keyword}, linkedIndex={type=long}, processDuration={type=long}}}"; line: 1, column: 3]];

JSON is valid:

{
      "properties": {
        "sessionId": {
          "type": "keyword"
        },
        "streamName": {
          "type": "keyword"
        },
        "_instance": {
          "type": "long"
        },
        "_update": {
          "type": "date"
        },
        "core": {
          "type": "long"
        },
        "episode": {
          "type": "long"
        },
        "fileIndex": {
          "type": "long"
        },
        "globalTimestamp": {
          "type": "date"
        },
        "id": {
          "type": "keyword",
          "index": false
        },
        "index": {
          "type": "long"
        },
        "name": {
          "type": "keyword",
          "normalizer": "lowercase"
        },
        "source": {
          "type": "keyword"
        },
        "subSource": {
          "type": "keyword"
        },
        "threadId": {
          "type": "long"
        },
        "timestamp": {
          "type": "long"
        },
        "type": {
          "type": "keyword"
        },
         "linkedIndex": {
          "type": "long"
        },
         "processDuration": {
          "type": "long"
        }
      }
    }

What could be the problem?

2

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