flowable / flowable/flowable-engine

Add history level persisting process instance variable without full activity history

Open
#3,664 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
7h 8m
Merged PRs (30d)
2

Description

**Is your feature request related to a problem? Please describe.**

I've been using `FULL` history level so far. There's a lot of redundant data that I don't need (and the tables get huge - tens of GBs) - mainly activity history (`act_hi_actinst`) and variable changes (`act_hi_detail`). I can easily get rid of the second one by using history level `ACTIVITY`.

Unfortunately, the activity's history is coupled with the variable's history. I really need the variables. I'm surprised that the `INSTANCE` history level is not including them. I really can't see what's the use of persisting instances without the variables.

**Describe the solution you'd like**

Ideally from my PoV the `INSTANCE` history level should also persist variables. If this is not a bug and it really makes sense for some users, then another level achieving the same thing works as well.

**Describe alternatives you've considered**

I'm considering background jobs clearing the `act_hi_actinst` table periodically.

**Additional context**

What further makes it worse is that:
- I'm having long-running processes with polling which further generates more activity history (by looping on the diagram).
- The variable updates are stored even when not changing anything (i.e. deleting not existing variable or setting the same value again).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.