attribute resolver behavior

[Cantor, Scott]

On 8/29/12 8:11 PM, "David Bantz" <dabantz at alaska.edu> wrote:

>Call me naive, but I presumed that resolvers would be invoked as needed
>by the release policy for a service.  The set of attributes needed for
>all SPs we support (and consequently the directory attributes needed) is
>much larger than the set for any one service, so the process the logs
>indicate - resolving all attributes defined, and then deleting all those
>not released to the current service - seems extravagant.  Is there a way
>to trigger resolution (if that's the right term) of only those attributes
>to be released in the current transaction with a specific SP?  Or is this
>inherently efficient enough that I shouldn't fret the additional overhead?

There's no way, the filter policies include plugins that can conditionally
evaluate things based on the data you resolve, so you can't filter first.
There's no way to know what the set will be.

If you have issues with efficiency, you can cache the results. Before
worrying you would be advised to test it and determine whether there's an
issue at all. Using locally cached data in MySQL is also an extremely good
strategy when you have sources that don't change mid-day.

-- Scott