Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Due to the breaking change in Elasticsearch 6.0, namely removal of mapping types and consequently changes in parent-child relationship, parent-child handling had to be updated.
Even though in Elasticsearch 6.0 it is a breaking change, I managed to keep the service API consistent, and continue support across the whole range of versions (2.4 - 6.3). The upgrade should not cause any problems for existing installations.
A few important notes:
esVersion
join
routing
core
container, which became a property of the service. The container is created for each service instance and selects appropriate versions of the core functions, based on the esVersion options. This ensures that dependencies between core functions are always valid.