You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "iilyak (via GitHub)" <gi...@apache.org> on 2023/08/01 19:41:50 UTC

[GitHub] [couchdb] iilyak commented on pull request #4710: feat(`mango`): strict index selection

iilyak commented on PR #4710:
URL: https://github.com/apache/couchdb/pull/4710#issuecomment-1660968293

   I agree with Nick that we would not want to put ourselves in the corner by embedding assumption about single index into endpoint name.
   
   I also agree with Bob and Jan that adding more option to existing endpoint is not the best choice in this particular case. Specifically because the option would be off by default for compatibility reasons. Also adding new options to existing API endpoints complicates maintaining of client libraries. 
   
   I think we should come up with a new endpoint name but shouldn't  embed index name into it.
   
   I am bad at naming and naming is hard.
   
   `/{dbname}/_find_indexed`
   `/{dbname}/_select`                                                  - // inspired by SQL
   `/{dbname}/_find_select`             - // find using selection of indexes
   
   Let's ask help from @ricellis who has an extensive experience in designing APIs.


-- 
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: notifications-unsubscribe@couchdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org