nickva opened a new pull request, #6103:
URL: https://github.com/apache/couchdb/pull/6103
Implement a new `/{db}/_index_info` endpoint to return the status of all the
indexes in the database in a single endpoint. It matches the general pattern of
`_dbs_infos` where we return the db info for all databases in a cluster. Just
like with `_db_infos`, where it doesn't return anything new just a better and
more optimized summary of all dbs, the new endpoint returns all the index
status in a single easy to use endpoint. User could, for example, fetch all the
design docs, parse them, and with an if/else check call a per-index specific
`_info` endpoint such as `/{db}/_design/{ddoc}/_info`,
`/{db}/_design/{ddoc}/_nouveau_info/{index}` etc. to get all this information,
but that's not very ergonomic and it's slower.
One of the main uses of this endpoint is to find out when all the indexes in
the db have been built. Each index returns an `updates_pending` object with the
pending bounds across all copies of each range. With a minimum (the best copy),
maximum (the worst copy) and a count of how many live copies returned a valid
result. This information is more accurate than what we might get with the view
group `_info` calls. It turns out for view groups `_info` we broke the
minimum/preferred/total `updates_pending` stats for view groups. That happened
when we switched the collection to work as a ring (the COUCHDB-3053 dedup fix),
so then only the first responding copy of each range is aggregated, total =
minimum and preferred only counts the responding shards. The new endpoint on
the other hand, waits and aggregates stats from all copies of the index.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
