Bug: Inconsistency definition of the correlation_id

[albert-cg]

Describe the bug Inconsistency in the definition of the correlation_id attribute in two tables. Same attribute but different length.

• postgres-persistence/src/main/resources/db/migration_postgres/V8__indexing.sql

CREATE TABLE workflow_index ( workflow_id VARCHAR(255) NOT NULL, correlation_id VARCHAR(128) NULL, workflow_type VARCHAR(128) NOT NULL, start_time TIMESTAMP WITH TIME ZONE NOT NULL, status VARCHAR(32) NOT NULL, json_data JSONB NOT NULL, PRIMARY KEY (workflow_id) );

• postgres-persistence/src/main/resources/db/migration_postgres/V1__initial_schema.sql

CREATE TABLE workflow ( id SERIAL, created_on TIMESTAMP DEFAULT CURRENT_TIMESTAMP, modified_on TIMESTAMP DEFAULT CURRENT_TIMESTAMP, workflow_id varchar(255) NOT NULL, correlation_id varchar(255), json_data TEXT NOT NULL, PRIMARY KEY (id) );

A clear and concise description of what the bug is.

Details Conductor version: 3.21.12 Persistence implementation: Postgres Queue implementation: Postgres Lock: N/A Workflow definition: N/A Task definition: N/A Event handler definition: N/A

Expected behavior Same type of definition

[JCHacking]

It would also be good to review the scripts of the rest of the persistence. I think the best thing to do is to create a new migration with the highest value in order not to break anything.