Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error while migrating to cloud: CONFLICT ON CONSTRAINT "uk-fieldlayout-fieldidentifier"

Lynx Technology Admin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2020

I'm trying to import a Jira Server (self hosted) zip exported backup into Jira Software cloud and getting this error:

An error occured during the import process.

Import again with a different backup file or get in touch with our support team. Include the steps you followed, along with any unique characteristics of your Jira setup.

Error importing data: java.lang.RuntimeException: com.querydsl.core.QueryException: Caught PSQLException for insert into "public"."fieldlayoutitem" ("fieldlayout", "fieldidentifier", "description", "ishidden", "isrequired", "renderertype") values (?, ?, ?, ?, ?, ?) ON CONFLICT ON CONSTRAINT "uk-fieldlayout-fieldidentifier" DO NOTHING

 

It sounds to me like uk-fieldlayout-fieldidentifier is a multicolumn index in the target server (Jira Cloud) for the table fieldlayoutitem.

When I check my table definition in the source server, both the FIELDLAYOUT and FIELDIDENTIFIER fields are listed as MUL:

mysql> describe fieldlayoutitem;
+------------------+---------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+------------------+---------------+------+-----+---------+-------+
| ID | decimal(18,0) | NO | PRI | NULL | |
| FIELDLAYOUT | decimal(18,0) | YES | MUL | NULL | |
| FIELDIDENTIFIER | varchar(255) | YES | MUL | NULL | |
| DESCRIPTION | text | YES | | NULL | |
| VERTICALPOSITION | decimal(18,0) | YES | | NULL | |
| ISHIDDEN | varchar(60) | YES | | NULL | |
| ISREQUIRED | varchar(60) | YES | | NULL | |
| RENDERERTYPE | varchar(255) | YES | | NULL | |
+------------------+---------------+------+-----+---------+-------+
8 rows in set (0.00 sec)

 

and these are the current indexes for the table: 

mysql> show index from fieldlayoutitem;
+-----------------+------------+-------------------------+--------------+-----------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment |
+-----------------+------------+-------------------------+--------------+-----------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| fieldlayoutitem | 0 | PRIMARY | 1 | ID | A | 1452 | NULL | NULL | | BTREE | | |
| fieldlayoutitem | 1 | idx_fli_fieldidentifier | 1 | FIELDIDENTIFIER | A | 90 | NULL | NULL | YES | BTREE | | |
| fieldlayoutitem | 1 | idx_fli_fieldlayout | 1 | FIELDLAYOUT | A | 17 | NULL | NULL | YES | BTREE | | |
+-----------------+------------+-------------------------+--------------+-----------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
3 rows in set (0.00 sec)

 

Judging by the error, I'd expect to see some duplicated entries for this query, but just returns empty:

mysql> select FIELDLAYOUT, FIELDIDENTIFIER, count(*) CNT from fieldlayoutitem group by FIELDLAYOUT, FIELDIDENTIFIER HAVING CNT>1;
Empty set (0.01 sec)

 

Does anyone know what could be causing this error during the import or how could I get a bit more information in the error message (debug) to at least get the actual values in the error rather than just 'values (?, ?, ?, ?, ?, ?)'.

Any help would be greatly appreciated.

Thanks,
Enrique

1 answer

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 25, 2020

Hello @Lynx Technology Admin

Thank you for reaching out.

We see that you've already opened an internal ticket with our support team, so we'll reach out to you in that ticket to further troubleshoot the error returned.

Best regards.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.3.4
TAGS
AUG Leaders

Atlassian Community Events