summaryrefslogtreecommitdiffstats
path: root/extra/elasticsearch/README.md
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2021-11-05 14:16:41 -0700
committerBryan Newbold <bnewbold@robocracy.org>2021-11-05 14:18:11 -0700
commitc87befeff80f609e0890ec608d9e65186ae528e8 (patch)
treef9d000d9e09ea89dbf45fe0b33c89ac3d2edd239 /extra/elasticsearch/README.md
parentee840a44990c02012955be860db5933493ea4b8a (diff)
downloadfatcat-c87befeff80f609e0890ec608d9e65186ae528e8.tar.gz
fatcat-c87befeff80f609e0890ec608d9e65186ae528e8.zip
api: add SQL 'ORDER BY' to many reads to stabilize API array ordering
The hope is to make things like file entity URLs, fileset manifests, and other arrays in the JSON API "stable", meaning that if you create an entity with a list of a given order, a read back (in any environment, including prod/QA, bulk dumps, etc) will return the array with the same sort order. This was informally happening most of the time, but occasionally not (!) Assumption is that these sorts will have little or no performance impact, as the common case is less than a dozen elements, and the hard cases are a few thousand at most, and there is already a sorted index.
Diffstat (limited to 'extra/elasticsearch/README.md')
0 files changed, 0 insertions, 0 deletions