How to manage tables in Camunda 7

[bijoy]

how to manage all those tables which are growing with process variables in camunda 7
Can we truncate those tables.
ACT_HI_VARINST is one of them I could see have all the process variables and it throws exception because one of the variable has character length more than 4000 ch.

was aborted: ERROR: value too long for type character varying(4000) Call getNextException to see other errors in the batch.
at org.apache.ibatis.executor.BatchExecutor.doFlushStatements(BatchExecutor.java:149)
at org.apache.ibatis.executor.BaseExecutor.flushStatements(BaseExecutor.java:129)
at org.apache.ibatis.executor.BaseExecutor.flushStatements(BaseExecutor.java:122)
at org.apache.ibatis.executor.CachingExecutor.flushStatements(CachingExecutor.java:114)
at org.apache.ibatis.session.defaults.DefaultSqlSession.flushStatements(DefaultSqlSession.java:252)
… 82 more
Caused by: java.sql.BatchUpdateException: Batch entry 1 insert into ACT_HI_VARINST (

[cpbpm]

@bijoy

ACT_HI_VARINST

The same question is answered in this thread:

Insert into ACT_HI_VARINST suddenly started failing due to Data truncation error

Hi Rob! Thank you very much, that was it. A JSON Object from a web service ended up growing much more than expected, so it took me by surprise, specially since the troublesome table was supposed to contain only historical data. Now, I agree that my understanding of Camunda’s data model is not too deep, and still haven’t dived a lot into it. I ended up giving the data a proper JSON serialization using the spin plugin, and took the opportunity to trim it into only the useful bits and only then …