Where are database column entity definitions stored?

[Rick Westbrock]

When I start up my development instance of JIRA 7.1.1 running against MySQL 5.7.16 I see 100 errors like the one below for various columns in various tables:

JIRA-Bootstrap ERROR      [o.o.c.entity.jdbc.DatabaseUtil] WARNING: Column "DESCRIPTION" of table "component" of entity "Component" is of type "MEDIUMTEXT(16777215)" in the database, but is defined as type "TEXT" in the entity definition.

Every error is for a column that has datatype mediumtext in the database and text in the entity defintion. Where can I find the entity definitions? The production instance has the same column datatypes but the log doesn't show these errors.

For context we restored the production database to dev, copied the jira and jira-home directories to the dev server and did some deprodification steps on config files and DB records. The application seems to be working just fine so far but I'd obviously prefer to find the root cause so we don't see these errors every time the app is restarted.

[Suren Raj]

Hi, Rick.

I found the following documentation which might help you:

• https://developer.atlassian.com/server/jira/platform/database-schema/

Cheers

[Rick Westbrock]

Thanks Suren, that is very helpful. I see in the entitymodel.xml file that this field is defined as very-long and the fieldtype-mysql.xml file shows that very-long is defined as sql-type="TEXT". I ran across this article that mentioned this type of error might show up on the first restart after an upgrade (it was an old article for upgrading from v3 to v4 I think) so I restarted the application but still get the errors.

I am not overly concerned about the errors however I am a little concerned that the production application which has the same entity definition XML files does not show these errors on startup. I'll proceed with a Support case to dig into it further.

[Noni Khutane]

Hi were you able to find a solution or an answer to this?

[Ivo]

Hi,

I have the same problem after upgrading from Jira 8.5 to 9.6 and MySQL 5.7 to 8.0. Has anybody found a solution to this?

[Sean Kim]

I too came across this error after upgrading MySQL from 5.7 to 8.0.

Can we get some feedback from Atlassian regarding this issue?

[Tommy van Extel]

Same issue here, anyone got around to fix this?