Open amaltaro opened 1 year ago
Thanks for starting this investigation @amaltaro. I have two questions here:
I didn't check the overall impact, but I am certain that it won't be a matter of a couple of days development. One use case is already known: acquiring work from global workqueue.
As long as we are in CouchDB 3.x, we can keep using it. Hopefully not for another 5 years after it's ended-of-life :-D
Quick update on this ticket, they have been deprecated in CouchDB 3.x, so we better start considering this development sooner than later.
One utilization example for this involves work acquisition between agent and global workqueue, example:
[notice] xxx GET /workqueue/_design/WorkQueue/_list/workRestrictions/availableByPriority?include_docs=true&descending=true&resources=%7B%22T2_CH_CERN_P5%22%3A+11379.0%2C+...+%22T2_HU_Budapest%22%3A+562.5%2C+%22T2_IT_Bari%22%3A+1905.0%7D&limit=2500&num_elem=2500&team=%22relval%22&skip=15000 200 ok 12872
Impact of the new feature WMCore in general
Is your feature request related to a problem? Please describe. As described in the CouchDB documentation: https://docs.couchdb.org/en/stable/ddocs/ddocs.html#list-functions
List and Show functions have already been deprecated in CouchDB 3.x and they will be completely removed in CouchDB 4.x
Describe the solution you'd like After discussing with CouchDB experts over Slack, we seem to have a few alternatives for that:
include_docs=true
, then process them in the client side. Using skip+limit parameters is discouraged for larger values though, as it is inefficient._find
APIDescribe alternatives you've considered See above
Additional context Lists are still functional in CouchDB 3.x, even though they are already considered deprecated.