Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Updating subject.properties search attributes

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Updating subject.properties search attributes


Chronological Thread 
  • From: "Black, Carey M." <>
  • To: Sean Mason <>, Grouper Users <>
  • Subject: RE: [grouper-users] Updating subject.properties search attributes
  • Date: Fri, 29 Mar 2019 03:43:17 +0000

Sean,

I think this is what you need...

https://spaces.at.internet2.edu/display/Grouper/Member+search+and+sort+columns

"
Sync Member Attributes
If you make a change to the sort or search strings, you should sync the
member attributes. For subjects that are people, you can use USDU:
"
There is a snip of GSH code to manually trigger the USDU utility.



You may also be able to trigger the USDU from the command line like this as
well.
$GROUPER_HOME/bin/gsh.sh -usdu <command line arguments>
-source <arg> find unresolvable subjects from source

Assuming it does the same thing with both invocations ( and I would guess
that it would ) limiting it to a specific source would make the most sense to
me.


On the other hand....
If you are sending yourself the daily reports then the USDU may have
already been run too.


NOTE: If your source has a lot of members, it may take a while to
complete.
I recently became aware that my "daily report" was always running the
USDU and "bad memberships" find functions. I change it to only run those one
day a week. The report takes over 3.5 hours when the USDU is run against 775k
Members. ( almost all from a single LDAP source ). However it runs in less
than 3 minutes when the USDU is not run on that day.

HTH.

--
Carey Matthew

-----Original Message-----
From:
<> On Behalf Of Sean Mason
Sent: Thursday, March 28, 2019 8:46 AM
To: Grouper Users <>
Subject: [grouper-users] Updating subject.properties search attributes

Hello Group(ers),

I improperly set the 'searchAttributeX' values in the upgrade from 2.3 to 2.4
a little while ago, which meant that the search_string0 - search_string3 were
not updated in the grouper_member table (probably among others) for new
memberships and groups since the upgrade.

I've just made the correction to subject.properties, and am now wondering if
there is a way to nudge Grouper to update those values for existing
memberships now that the subject.properties file has been changed?

Thanks,
Sean



Archive powered by MHonArc 2.6.19.

Top of Page