New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postgres indexing problem with task_type length #111
Comments
I have faced exactly the same issue, had to revert back to ES indexing |
OK - should be pretty straightforward to change the column length in the database schema for this |
1 task
I think this issue can be closed |
looks good in version 3.19.0 |
@vinize was the code updated to insert the type instead of the name in the task_type column, i only see a PR for making the field length longer? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When changing the indexing database from elastic to postgres, an error occurs related to the length of the task name.
It turns out that there is a problem with the length of the task_type field. According to the database schema, it should be up to 32 characters long. However, in the case of SIMPLE tasks, the task_name values go there instead of task_type
Details
Conductor version: 3.18
Persistence implementation: Postgres
Queue implementation: Redis
Lock: Redis
Workflow definition:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
In case on simple tasks value 'SIMPLE' should be inserted to task_type column, or task_type column should be extended to 255 length (like task_name)
Additional context
bug initially reported at: Netflix/conductor-community#252
The text was updated successfully, but these errors were encountered: