fix(sonarqube): increase cq_issues and cq_file_metrics project_key length to 500#8783
Merged
Conversation
dosubot
Bot
added
size:M
jbsmith7741
force-pushed
the
sq_data_too_long
branch
from
692fbb5 to
df0b5a9
Compare
la-tamas
pushed a commit
to archfz/incubator-devlake
that referenced
this pull request
Mar 26, 2026
la-tamas
pushed a commit
to archfz/incubator-devlake
that referenced
this pull request
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The project_key column in cq_issues and cq_file_metrics were too short to hold the domain-layer project ID generated by didgen (format: sonarqube:SonarqubeProject::). Since SonarQube allows project keys up to 400 characters, the generated domain ID can be around ~450 characters, which will cause the "Data too long for column" error. This changes the columns cq_issues and cq_file_metrics to varchar(500) which allows for the long names and is consistent with DomainEntityExtended.Id
Does this close any open issues?
Closes #8331
Screenshots
N/A
Other Information
Added migration script (20260317_increase_cq_issues_project_key_length) to alter both columns on the next startup.