elasticsearch-dump: illegal_argument_exception: [routing] is missing for join field [joinField]
- ElasticDump version: 3.3.19
- Elasticsearch version: 6.3.0
- Node.js version (note that nodejs v8+ is required for this tool): v9.11.2
- Full command you are having issue with (with inputs and outputs)
Exporting to file (works):
#!/usr/bin/env bash
elasticdump \
--input=http://10.0.0.1:9200/index \
--output=/data/index-mapping.json \
--type=mapping
elasticdump \
--input=http://10.0.0.1:9200/index \
--output=/data/index-analyzer.json \
--type=analyzer
elasticdump \
--input=http://10.0.0.1:9200/index \
--output=/data/index-data.json \
--type=data
importing from file on another server (doesn’t work)
#!/usr/bin/env bash
elasticdump \
--input=index-analyzer.json \
--output=http://127.0.0.1:9200/index \
--type=analyzer
elasticdump \
--input=index-mapping.json \
--output=http://127.0.0.1:9200/index \
--type=mapping
elasticdump \
--input=index-data.json \
--output=http://127.0.0.1:9200/index \
--type=data
It fails with:
{ _index: 'index',
_type: 'doc',
_id: 'article-112437',
status: 400,
error:
{ type: 'mapper_parsing_exception',
reason: 'failed to parse',
caused_by:
{ type: 'illegal_argument_exception',
reason: '[routing] is missing for join field [joinField]' } } }
Currently working on a simple data set to reproduce.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 19
@ferronrsmith Can you verify the analysis of @todvora and reopen the issue? Thanks!
I can confirm the issue for the following versions:
The dataset that causes this is around 30GB, so still working on providing a simple dataset to reproduce.