Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

you can bump it up a little, we meant to address that already and will adjust it soon in a grouper upgrade 🙂

---

From: <> on behalf of Black, Carey M. <>
Sent: Monday, June 1, 2020 5:01 PM
To: Sean Mason <>; Grouper Users <>
Subject: RE: [grouper-users] Stem display_name column length

 

Sean,

 

I don’t think that is necessary.

 

“I would expect” (emphasis on the “I”) a  *possible* issue if the autoDDL ever needed to make a change to that table during an upgrade after a deployer made a manual change. But I would not expect it to be affected just yet.

   So my question is more a theoretical one than a “known issue” one.

 

And I don’t think 2.5.30 is “official yet”…. So don’t go there… yet…

 

--

Carey Matthew

 

From: Sean Mason <>
Sent: Monday, June 1, 2020 4:24 PM
To: Black, Carey M. <>; Grouper Users <>
Subject: RE: Stem display_name column length

 

Ahh, right!

 

I just set that parameter when building the upgrade and it already slipped my memory…

 

I’m willing to bump up my development instance to i2incommon/grouper:2.5.30 from i2incommon/grouper:2.5.29 if you think that will help form an answer to this auto DDL question?

 

From: Black, Carey M. <>
Sent: Monday, June 1, 2020 3:39 PM
To: Sean Mason <>; Grouper Users <>
Subject: RE: Stem display_name column length

 

Sean,

 

NOTE: I wonder how this will “work” with the current v2.5 “ddl auto update” tooling too.

 

Meaning making any change from the “expected” could lead to issues when you move forward to the next container.

I suggest that any advancement in the container be used with caution.

 

 

I wonder if this “plan” is dealt with in the “auto ddl world” ?

 

--

Carey Matthew

 

From: Sean Mason <>
Sent: Monday, June 1, 2020 3:24 PM
To: Black, Carey M. <>; Grouper Users <>
Subject: RE: Stem display_name column length

 

That does indeed help, an increase in size to the schema and adding grouper.stemName.maxSize = <larger number here> to grouper.properties has cleared the issue.

 

Thank you for your help!

Sean.

 

From: Black, Carey M. <>
Sent: Monday, June 1, 2020 3:03 PM
To: Sean Mason <>; Grouper Users <>
Subject: RE: Stem display_name column length

 

Sean,

 

I found this:   https://todos.internet2.edu/browse/GRP-1807

 

So it looks like there is a planned way to do this.

 

HTH.

 

--

Carey Matthew

 

From: <> On Behalf Of Sean Mason
Sent: Monday, June 1, 2020 9:25 AM
To: Grouper Users <>
Subject: [grouper-users] Stem display_name column length

 

Hi There,

 

I’ve been working on upgrading our Grouper v2.4 instance to 2.5 and things are going very well now that I’ve (somewhat) wrapped my head around Docker.  The system has really been a star in our IAM system renewal efforts.

 

One thing I have noticed that I’ve missed in our installation (this is not a problem resulting from the upgrade) is that the maximum length of the display_name field for grouper_stems is 255 characters.  We have some HR org data that (believe it or not) exceeds this length.

 

Is it safe for me to extend the length of that field in the schema?  If not is it possible the length of the field could be made to match the length of the display_name field in the grouper_groups table in an upcoming version?

 

Thank you,

Sean