Hm, ok.. no we don't currently support that.
As a workaround, you could of course just do
?fields=:all,children[:all,children[:all]], i.e. :all,children[:all] for as
many levels as you have, its a bit of a hack, but it would work (if you add
too many, it will just be ignored)
If its only two, you
You mean children, or descendants? if you just want the full view of the
children of a few OUs you could probably get away with
?fields[:all,children[:all]] ?
--
Morten
On Fri, Sep 5, 2014 at 12:18 PM, Mahendra Kariya <
mahendra.kar...@thoughtworks.com> wrote:
> OK.
>
> So we need all fields f
On Fri, Sep 5, 2014 at 11:55 AM, Mahendra Kariya <
mahendra.kar...@thoughtworks.com> wrote:
> It looks like attributeValues field takes most of the time. We have around
> 6-7 custom attributes for each orgUnit. We don't need all of these. We only
> need the value of one particular attribute. Is th
Do you need all fields? you could probably easily shave of a quite a few
bytes by only asking for the fields you need. We only support compression
on the /api/metadata endpoint (zip, gzip) and I would rather see
compression implemented in the caching server / proxy (nginx, lighty etc).
You can also
4 matches
Mail list logo
