polx opened a new issue, #5500: URL: https://github.com/apache/couchdb/issues/5500
There seems to be no documentation on how to define what is indexed as part of the map-reduce process of design-documents yielding views. ## Description I have been searching a fair amount of the web and could not find an answer. In Lucene/Solr (for example), an index is built by document-fields' some of which are indexed (and thus queried for), some of which are stored (and thus returned with the query). We have been developing a webapp in NodeJS with a fair amount of views connected through Nano and start encountering timeouts and other surcharge signs. I managed to add indexed-field-names in the mango-query Fauxton UI. But I did not find the equivalent for design-documents. It's interesting becasue a lot of the documentation about views and design documents speak about the view generating an index. However... with what? ## Steps to Reproduce Read the the [design documents documentation](https://docs.couchdb.org/en/stable/ddocs/index.html) and expect to be informed on what is indexed. ## Expected Behaviour ... nothing is said on what is indexed. - - Maybe it is "all". If yes, it needs to be said! (then I'll move the mass out of the views) - Maybe it is subtly created by usage (then we should tune usage). ## Your Environment couchdb "Welcome" version "3.4.2" git_sha "6e5ad2a5c" uuid "b7e4949c25ca9a1d481d30a05e127e69" * Browser name and version: Firefox 137.0 * Operating system and version: The server is running on Ubuntu 22.04.5 LTS and the CouchDB is installed as a debian package. ## Additional Context - some of the documents can be as big as 30 Mb (yes, this is wrong, I know) - a natural expectation of the views is that it gives a window to distilled-data-masses, so that a single query would give you the access to the mass without costing that much in ram... I guess that this expectation is wrong but I would love to be guided. -- 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]
