Right now, the broker takes the attribute list in "attrs"/"pick" and forwards that list in the URI param.
Unfortunately, this is not quite correct.
There might be other attributes in 'q', 'geometryProperty', 'geoproperty', 'orderBy'. 'pick'.
The broker needs to extract all attributes from all of those URI params and create a new value of "attrs" ("pick").
The projection (removing not wanted attributes) is done after the complete entity array has been created.
Note also that 'q' (and possibly more URI params are NOT to be forwarded). The 'q' selection must be done afterwards.
See issue #1848 for more details.
Right now, the broker takes the attribute list in "attrs"/"pick" and forwards that list in the URI param.
Unfortunately, this is not quite correct.
There might be other attributes in 'q', 'geometryProperty', 'geoproperty', 'orderBy'. 'pick'.
The broker needs to extract all attributes from all of those URI params and create a new value of "attrs" ("pick").
The projection (removing not wanted attributes) is done after the complete entity array has been created.
Note also that 'q' (and possibly more URI params are NOT to be forwarded). The 'q' selection must be done afterwards.
See issue #1848 for more details.