Grouper Users - Open Discussion List

["Gettes, Michael" <>]

I’m interested in answers to these questions as well.  I didn’t change names 
but I have removed configuration of changelog consumers with orphaned entries 
in the grouper_change_log_consumer table - so I just go into that table and 
delete the appropriate row.  Didn’t seem to break anything.

/mrg

> On Jan 30, 2019, at 2:21 PM, Black, Carey M. <> wrote:
> 
> Q1) Are there any docs on what should be done to clean up after a change 
> log consumer is "decommissioned"?
> 
> I recently changed the name of a change log consumer and now I have a 
> remnants of data in the Grouper DB that has the old name value. (and 
> another row for a CLC that I stopped using after a proof of concept testing 
> with it. ) Which lead me to the question above.
> 
> NOTE: At a minimum, I can see that row(s) are left in:
>       grouper_change_log_consumer
> 
> Q2) Are there any other references that I have not found yet?
> Q3)  Is it "ok" ( and expected ) to delete rows from 
> grouper_change_log_consumer table when they are permanently orphaned?
> Q4) Is there any way to do this without resorting to SQL?  (AKA: A grouper 
> API call that is the "planned way" to clean this up? Even a manual 
> method/process to kick off?)
> Q5) Are there any Grouper API's around the CLC for things like:
>       ] add/remove/rename
>       ] status ( things like number of events not yet processed, per CLC or 
> ) for a given CLC) )
> 
>       I know there are ways to force a "run" (via a gsh function:  
> loaderRunOneJob("CHANGE_LOG_<name_goes_here>"); ) Looking for the "rest of 
> the story".... :)
> 
> 
> Thanks in advance.
> 
> -- 
> Carey Matthew 
> 
>