Fix activity variable size limit bug #274
Merged
Conversation
This file contains 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
The activity json string input variable might be too big to be stored in DB (4000 characters limit), e.g. the activity json string contains a variable being resolved at runtime with a more than 4000 characters string value, when camunda persists this new activity json string as variable in DB, it fails with an exception. This commit fixed this issue by definiting the input activity string in a map instead of string, the map object is stored in bytearray table as BLOB type without limit.
ystxn
approved these changes
Jun 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The activity json string input variable might be too big to be stored in DB (4000 characters limit), e.g. the activity json string contains a variable being resolved at runtime with a more than 4000 characters string value, when camunda persists this new activity json string as variable in DB, it fails with an exception.
This commit fixed this issue by definiting the input activity string in a map instead of string, the map object is stored in bytearray table as BLOB type without limit.
Description
Please put here the intent of your pull request.
Dependencies
List the other pull requests that should be merged before/along this one.
Checklist