Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Alert Server Changes - Implement message ID field #5994
To efficiently get large number of messages from Elasticsearch, we have to use search-after queries in the future. Pagination or scrolling is not efficient and can lead to high load situations in Elasticsearch.
The usage of search-after queries requires the usage of a tie-breaker field for sorting the results. (see search-after documentation) This tie-breaker field must have a unique value per document in Elasticsearch. The
Since we don't have such a field at the moment, we have to add one now so we can use search-after queries in the future.