UBERF-4526: Elastic bulk error on re-indexing #4155
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.
Contribution checklist
Brief description
The error we have is "Limit of total fields [1000] has been exceeded while adding new fields [1]". Added this text to error log to make such errors visible.
This is happens in index with a lot of custom fields and is about the amount off custom field names we have overall in one elastic index among all the elastic documents.
Although it is possible just to increase this limit, I would rather prefer not to do that due to performance risks.
And because we do not use actual field name in searching or filtering I suggest to move from field names like
638611f18894c91979399ef3%Источник_6386125d8894c91979399eff
to have one custom attribute field and have all custom fields there as nested label-value objects.Checklist
Related issues
A list of closed updated issues
Contributor requirements