Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Grouper and MariaDB

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Grouper and MariaDB


Chronological Thread 
  • From: "Redman, Chad" <>
  • To: Richard Frovarp <>, " Mailing List" <>
  • Subject: RE: [grouper-users] Grouper and MariaDB
  • Date: Wed, 6 Feb 2019 14:54:50 +0000

From my reading, it does sound like that is the fix. It's an issue specific
to InnoDB plus COMPACT or REDUNDANT row format. The limit for utf8mb4 would
be 191 bytes, so there will probably be a lot more errors like that. -Chad

-----Original Message-----
From:
[] On Behalf Of Richard Frovarp
Sent: Wednesday, February 06, 2019 9:37 AM
To: Mailing List <>
Subject: [grouper-users] Grouper and MariaDB

How does one get Grouper 2.4 to work with MariaDB 10.1? I'm running into
the "Index column size too large. The maximum column size is 767 bytes."
error. Using utf8mb4.

I'm following the instructions from here:
https://spaces.at.internet2.edu/display/Grouper/Grouper+book+-+Setting+up+the+repository+database

I'm using the org.hibernate.dialect.MariaDB10Dialect dialect in
grouper.hibernate.properties.

I haven't gone through and fully inspected the generated file, but this
is generating the first error:


CREATE TABLE grouper_members
(
    id VARCHAR(40) NOT NULL,
    subject_id VARCHAR(255) NOT NULL,
    subject_source VARCHAR(255) NOT NULL,
    subject_type VARCHAR(255) NOT NULL,
    hibernate_version_number BIGINT,
    subject_identifier0 VARCHAR(255) NULL,
    sort_string0 VARCHAR(50) NULL,
    sort_string1 VARCHAR(50) NULL,
    sort_string2 VARCHAR(50) NULL,
    sort_string3 VARCHAR(50) NULL,
    sort_string4 VARCHAR(50) NULL,
    search_string0 VARCHAR(2048) NULL,
    search_string1 VARCHAR(2048) NULL,
    search_string2 VARCHAR(2048) NULL,
    search_string3 VARCHAR(2048) NULL,
    search_string4 VARCHAR(2048) NULL,
    name VARCHAR(2048) NULL,
    description VARCHAR(2048) NULL,
    context_id VARCHAR(40) NULL,
    PRIMARY KEY (id)
);

CREATE UNIQUE INDEX member_subjectsourcetype_idx ON grouper_members
(subject_id, subject_source, subject_type);

Is there a setting I need? I think adding ROW_FORMAT=DYNAMIC should fix
it, but wondering if there is an easier way. Or do I need a newer
MariaDB? Or should I be opening an issue?

Thanks,

Richard




Archive powered by MHonArc 2.6.19.

Top of Page