...
[13:57:57 CDT(-0500)] <EricDalquist> but it ensures that you're doing a pull for just the commits you want to
[14:01:32 CDT(-0500)] <athena> ugh. i ran initportal and it ate all my stats data 
[14:01:35 CDT(-0500)] <athena> totally wasn't thinking
[14:01:39 CDT(-0500)] <EricDalquist>
[14:01:50 CDT(-0500)] <EricDalquist> I have 10GB worth here 
[14:01:56 CDT(-0500)] <athena> lol
[14:01:57 CDT(-0500)] <athena> well
[14:01:59 CDT(-0500)] <EricDalquist> well from our 2 weeks of being live on 4.0
[14:02:04 CDT(-0500)] <athena> i'll check this stuff in today and you can test it?
[14:02:16 CDT(-0500)] <EricDalquist> I'll see if I can
[14:02:19 CDT(-0500)] <athena> ok
[14:02:22 CDT(-0500)] <EricDalquist> we don't have aggregation on yet
[14:02:26 CDT(-0500)] <athena> so, last stats question (i hope)
[14:02:27 CDT(-0500)] <athena> ah.
[14:02:28 CDT(-0500)] <EricDalquist> but I can do it in a non-prod env
[14:02:38 CDT(-0500)] <athena> even if you happen to have data in your local db
[14:03:10 CDT(-0500)] <athena> we have an API for retrieving all the group aggregations i assume?
[14:03:51 CDT(-0500)] <EricDalquist> AggregatedGroupLookupDao
[14:03:56 CDT(-0500)] <EricDalquist> looks like it is missing some utility APIs
[14:04:05 CDT(-0500)] <EricDalquist> like listing all of the aggregations
[14:04:07 CDT(-0500)] <athena> lol
[14:04:09 CDT(-0500)] <athena> ok
[14:04:16 CDT(-0500)] <athena> so that's the last piece we'd need, i think
[14:04:23 CDT(-0500)] <EricDalquist> thats what happens when I write it only thinking about putting data in 
[14:04:29 CDT(-0500)] <EricDalquist> should be a very easy fix though
[14:04:39 CDT(-0500)] <athena> cool 
[14:14:46 CDT(-0500)] <athena> ok, what do the group mappings look like?
[14:14:53 CDT(-0500)] <athena> is groupName the string name or the id?
[14:15:59 CDT(-0500)] <EricDalquist> ID, GROU_SERVICE, GROUP_NAME
[14:16:15 CDT(-0500)] <EricDalquist> where ID is a synthetic identifier specific to the group mapping table
[14:16:45 CDT(-0500)] <EricDalquist> so like a login event lists all the groups a user is in via the group keys: pags.everyone
[14:17:25 CDT(-0500)] <EricDalquist> during aggregation "pags.everyone" is resolved by the groups API to its actual IEntityGroup
[14:18:12 CDT(-0500)] <EricDalquist> and then a row is found or created for the service "pags" and the name "Everyone"
[14:18:23 CDT(-0500)] <athena> ok
[14:18:28 CDT(-0500)] <EricDalquist> the goal is to de-couple the aggregation data from the actual portal data
[14:18:44 CDT(-0500)] <EricDalquist> so that if someone changes the name of, or deletes, a group
[14:18:51 CDT(-0500)] <EricDalquist> it doesn't break a bunch of already aggregated data
[14:18:53 CDT(-0500)] <athena> makes sense
[17:04:18 CDT(-0500)] <athena> EricDalquist: is there a reason we can't query group mappings by id or is that just an oversight?
[17:04:28 CDT(-0500)] <EricDalquist> just oversight
[17:04:35 CDT(-0500)] <EricDalquist> I only wrote the APIs I needed at the time
[17:06:08 CDT(-0500)] <athena> ok
[17:06:17 CDT(-0500)] <athena> i think we probably need to just hold off for 4.0.6 at this point
[17:06:28 CDT(-0500)] <athena> unless you run into something that delays 4.0.5 another day or two
[17:06:33 CDT(-0500)] <EricDalquist> ok
[17:06:43 CDT(-0500)] <athena> really close though
[17:06:53 CDT(-0500)] <athena> and then we'll have pretty happy graphs
[17:11:26 CDT(-0500)] <mmoayyed> Folks, question on LdapPersonAttributeDao. Do you mind exlaining how the queryAttributeMapping property is used?
[17:12:10 CDT(-0500)] <mmoayyed> I am having trouble understanding how the query wrt to the attr map defined there is generated