Change how nested objects are indexed #404
Merged
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.
Description
This is a proposed fix for a bug discovered in Clowder process for indexing extractor metadata into Elasticsearch. The previous code would inadvertently cast nested JSON objects as long JSON strings in some cases where arrays were being used, this PR modifies the indexer to retain the JSON structure. Features like ES type inference (double vs. string for example) is maintained.
Affected instances would need to do the following to refresh/correct the search index:
POST /api/deleteindex
POST /api/reindex (this does not delete the index first, must do it manually)
Review Time Estimate
Types of changes
Checklist: