Arvados

For the 'get' case, would it be useful to have a 'deselect' param so that we don't need to update clients (e.g., wb2) when new fields are added to collections while avoiding getting the manifest_text included in the response?

18122-select-param @ 5d7bef4122c59bec9145f2853b76170b4ddca67f -- developer-run-tests: #2692

Confirmed that only the selected columns are loaded from the database (except in the case of "update", which needs to populate all attributes in order to do validations).

18122-select-param @ 7563e6276baade41eb3faa3ff167abab1cb0f890 -- developer-run-tests: #2694

Here're my comments/questions:

• In file services/api/app/controllers/application_controller.rb: In the _requires_parameters methods, should descriptions be added for the automatic cli help?
• Word repetition in file doc/api/methods.html.textile.liquid:L87: "...whose whose..."
• Do you think it would be helpful to document the particular behavior when requesting a collection by PDH? (i.e., we can use select to "deselect" manifest_text)

Lucas Di Pentima wrote:

• In file services/api/app/controllers/application_controller.rb: In the _requires_parameters methods, should descriptions be added for the automatic cli help?

Good point, added

• Word repetition in file doc/api/methods.html.textile.liquid:L87: "...whose whose..."

Fixed, thanks

• Do you think it would be helpful to document the particular behavior when requesting a collection by PDH? (i.e., we can use select to "deselect" manifest_text)

Updated the relevant part of the api/methods/collections page -- is this better?

18122-select-param @ bc146037e1aa617739c0a3859727066c9304829a -- developer-run-tests: #2696

Thanks! this LGTM.