This repository has been archived by the owner on Aug 9, 2022. It is now read-only.
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.
Rest Layer and Async Search Cleanup Management #9
Rest Layer and Async Search Cleanup Management #9
Changes from 1 commit
9c921d2
591d8ad
28d39b7
93ecef5
959439a
1bbf255
9fc6a89
0678622
c830645
7cbcbf8
97d65c4
ceecbac
903b107
85fed8f
6f24bf0
a62f6cb
c7b2df1
d072d6d
fa5cd67
bc64fc3
3350aa8
d504524
c164993
b71e57f
362ab77
99aacde
cfac793
30c3a66
34865ca
0878892
8173ba0
150ad90
f90d6be
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why have such long field names?Won't you have a section for async search and then add status, current directly there. Asking because long fields may take longer for serialization and deserialization depending on algo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trimming
asynchronous_search_
prefix from individual stats