<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Oct 21, 2014 at 10:37 AM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I had a concern about whether the mergeResults option in LDAP is making<br>
sense. When I read the docs on that option in the schema, I couldn't map<br>
that to what the Javadoc for the ldaptive class that it apparently<br>
triggers the use of was saying. They didn't seem quite the same to me.<br></blockquote><div><br></div><div>You're correct. That didn't get ported correctly, but it leads me to another question. In v2, the LDAPDataConnector always returned a single LDAP entry. A deployer would use the mergeResults option if they needed attributes from multiple entries. The change in r6746 always merges all the attributes from all entries, so I don't think that option is needed anymore. No idea if anyone was relying on this as a negative feature, if so we may want a switch to disable merging of results.</div><div><br></div><div>Sorry if that doesn't make sense, I've had a lot of NyQuil the past few days...</div><div><br></div><div>--Daniel Fisher</div><div><br></div></div></div></div>