Grouper Users - Open Discussion List

[Chris Hyzer <>]

Btw, the purpose is to order and assign a sequential increasing number to each event… (since they are occurring in various transactions and connections and processes and we aren’t relying on database vendor specific sequences.

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Kediyal, Prashant
Sent: Friday, February 13, 2015 12:54 PM
To:
Subject: [grouper-users] change_log_entry_temp vs change_log_entry

 

Hi,

 

We have been having a few cases where we see valid web service requests that get logged in the web services log but don’t get provisioned through our change log consumer code.

 

When we look at the change log entry table we don’t see the record corresponding to the one logged in the web service log but we see it in  change_log_entry_temp. I am assuming

That only the records in  change_log_entry result in an invocation of our change log consumer. Question is what is the use of the  change_log_entry_temp and if it is a temporary holding table, then when will the record move to  change_log_entry so that our change log consumer receives it and then proceeds to provision to our LDAP.

 

Any suggestions?

 

—Prashant