[SQSERVICES-1828] pagination of team members does not work properly for certain team sizes#2968
Conversation
ae96ae1 to
a741fba
Compare
| where | ||
|
|
||
| sortingTieBreaker :: [ES.DefaultSort] | ||
| sortingTieBreaker = [ES.DefaultSort (ES.FieldName "_doc") ES.Ascending Nothing Nothing Nothing Nothing] |
There was a problem hiding this comment.
I'm not sure, but this looks like something different from what the docs you are linking suggest, and it may be prohibitively inefficient.
Can you try the _id trick that you were about to try? That may require an ES migration, but we've done those before, and ES doesn't server as a source of truth and in the worst case can recover from Cassandra. So I'm not too worried.
Co-authored-by: fisx <mf@zerobuzz.net>
Co-authored-by: fisx <mf@zerobuzz.net>
Co-authored-by: fisx <mf@zerobuzz.net>
There was a problem hiding this comment.
I can't parse (or understand) this sentence.
362f3e6 to
b19a3b3
Compare
fisx
left a comment
There was a problem hiding this comment.
maybe you can add something to the swagger docs of the /search endpoint along the lines of "if you can, use /list-users, /search is more powerful but potentially more expensive and less reliable"? not sure.
But is that really true? |
|
ci seems in trouble: |
https://wearezeta.atlassian.net/browse/SQSERVICES-1828
Checklist
changelog.d