- Issue created by @Nadim Hossain
- 🇦🇺Australia Nadim Hossain
Added a patch against 1.x for my project use until I upgrade it to 2.x
The ElasticSearchDatasetPipeline plugin currently triggers an error message in its constructor unconditionally, warning that:
Mappings that are defined at the top level of your pipeline will no longer take effect. Please place them under:
destinationSettings:
elasticsearch:
mappings:
...
However, this warning is displayed regardless of whether mappings are actually defined at the top level or correctly placed under destinationSettings.elasticsearch.mappings. This causes confusion because the error appears even when the configuration is valid.
1. Define Elasticsearch mappings correctly under:
destinationSettings:
elasticsearch:
mappings:
properties:
field_name:
type: keyword
2. Run the pipeline or trigger the constructor.
3. The warning message about deprecated top-level mappings appears regardless.
Add a check in the constructor to detect if top-level mappings are actually set and destinationSettings.elasticsearch.mappings are empty before triggering the warning.
Active
2.0
Code
Added a patch against 1.x for my project use until I upgrade it to 2.x