Skip to Content.
Sympa Menu

grouper-users - [grouper-users] change_log_entry_temp vs change_log_entry

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] change_log_entry_temp vs change_log_entry


Chronological Thread 
  • From: "Kediyal, Prashant" <>
  • To: "" <>
  • Subject: [grouper-users] change_log_entry_temp vs change_log_entry
  • Date: Fri, 13 Feb 2015 17:53:43 +0000
  • Accept-language: en-US
  • Authentication-results: internet2.edu; dkim=none (message not signed) header.d=none;

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



Archive powered by MHonArc 2.6.16.

Top of Page