N8N (docker latest version) Elasticsearch / Create Index with Mapping / Problem

Questions
1

Hi,
I’m trying to create an index in elasticsearch with the elasticsearch node. It’s works but the mapping I give is not taken into account. I have no field in my index. The mapping object is correct because I took it from another index already created directly with elasticsearch.
If you have an idea…
Thx

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
4

Hi @Phildefer, welcome to the community.

I am sorry you are having trouble. I am not quite sure how to reproduce the problem based on the information you have provided unfortunately. However, seeing you already have this working outside of n8n I’d suggest you simply use the HTTP Request here node to recreate your existing API and send it to your Elasticsearch instance.

1 Like
5

HI, and thank you for your answer.
I’m not sure to know what to do with the API. I’m a very basic user of elasticsearch.

here is my mapping
{
“mappings”: {
“_meta”: {
“created_by”: “file-data-visualizer”
},
“properties”: {
“@timestamp”: {
“type”: “date”
},
“actor1”: {
“type”: “keyword”
},
“actor2”: {
“type”: “keyword”
},
“admin1”: {
“type”: “keyword”
},
“admin2”: {
“type”: “keyword”
},
“admin3”: {
“type”: “keyword”
},
“assoc_actor_1”: {
“type”: “keyword”
},
“assoc_actor_2”: {
“type”: “keyword”
},
“civilian_targeting”: {
“type”: “keyword”
},
“country”: {
“type”: “keyword”
},
“disorder_type”: {
“type”: “keyword”
},
“event_date”: {
“type”: “date”
},
“event_id_cnty”: {
“type”: “keyword”
},
“event_type”: {
“type”: “keyword”
},
“fatalities”: {
“type”: “long”
},
“geo_precision”: {
“type”: “long”
},
“inter1”: {
“type”: “long”
},
“inter2”: {
“type”: “long”
},
“interaction”: {
“type”: “long”
},
“iso”: {
“type”: “long”
},
“latitude”: {
“type”: “double”
},
“location”: {
“type”: “keyword”
},
“longitude”: {
“type”: “double”
},
“notes”: {
“type”: “text”
},
“point_location”: {
“type”: “geo_point”
},
“region”: {
“type”: “keyword”
},
“source”: {
“type”: “text”
},
“source_scale”: {
“type”: “keyword”
},
“sub_event_type”: {
“type”: “keyword”
},
“tags”: {
“type”: “keyword”
},
“time_precision”: {
“type”: “long”
},
“timestamp”: {
“type”: “date”,
“format”: “epoch_second”
},
“year”: {
“type”: “long”
}
}
}
}

6

Finally I found the solution with the HTTP request.
Thx!

1 Like
7

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