Thanks! > comp sci theoretically nothing that’ll be any more > efficient internally than the obvious map/reduce view
This probably doesn’t hold in real world at least for DBs you know upfront have number_of_partitions ≃ number_of_docs < several_thousands. Reading all _id-s without reduce is likely cheaper in that case. Which means I might just read _id-s for DBs having say < 10k docs, without writing a ddoc with map/reduce view and waiting it to warm up. Or I can allow user to choose what to do. ermouth пн, 25 мая 2020 г. в 01:58, Paul Davis <[email protected]>: > Currently no, and comp sci theoretically nothing that’ll be any more > efficient internally than the obvious map/reduce view. > > On Sun, May 24, 2020 at 12:48 PM ermouth <[email protected]> wrote: > > > Hi devs, > > > > is there a way to get the list of DB partitions, except dedicated > > map/reduce? Trying to add partitioned queries UI into Photon and bit > stuck > > how to implement it. > > > > ermouth > > >
