[Fix #3480] Changing jsonb to varchar

[fjtirado]

Fixes https://github.com/apache/incubator-kie-kogito-runtimes/issues/3480

[kie-ci3]

PR job #7 was: UNSTABLE Possible explanation: This should be test failures

Reproducer

build-chain build full_downstream -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3484 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3484/7/display/redirect

Test results:

• PASSED: 2867
• FAILED: 1

Those are the test failures:

org.kie.kogito.mongodb.transaction.AbstractTransactionManagerIT.testAbort

Command failed with error 246 (SnapshotUnavailable): 'Unable to read from a snapshot due to pending collection catalog changes; please retry the operation. Snapshot timestamp is Timestamp(1713883869, 0). Collection minimum is Timestamp(1713883869, 2)' on server 172.18.0.1:32799. The full response is {"errorLabels": ["TransientTransactionError"], "operationTime": {"$timestamp": {"t": 1713883868, "i": 6}}, "ok": 0.0, "errmsg": "Unable to read from a snapshot due to pending collection catalog changes; please retry the operation. Snapshot timestamp is Timestamp(1713883869, 0). Collection minimum is Timestamp(1713883869, 2)", "code": 246, "codeName": "SnapshotUnavailable", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1713883869, "i": 3}}, "signature": {"hash": {"$binary": {"base64": "AAAAAAAAAAAAAAAAAAAAAAAAAAA=", "subType": "00"}}, "keyId": 0}}}

[deepakkapoor23]

This doesn't really address #3469, only affects JDBC persistence...but that's enough for my use case right now. Thanks @fjtirado

[fjtirado]

This doesn't really address #3469, only affects JDBC persistence...but that's enough for my use case right now. Thanks @fjtirado

You are right, MongoDB is not relational ;)