history level cannot be changed

[Falko Menge]

The documentation says: 'Note that when using the dafault history
backend, the history level is stored in the database and cannot be
changed later.'

Is there any workaround to change the history level, e.g., by emptying
the history tables?

--
We are hiring: http://www.camunda.com/jobs/

[Bernd Rücker (camunda)]

Hi Falko.

IMHO you just have to make sure to adjust the flag in the database
according to your processEngineConfiguration. If you adjust both
everything works fine. But you have to be aware that the level is not
consistent in the database entries.

Cheers
Bernd

-----Urspr�ngliche Nachricht-----
Von: camunda-...@googlegroups.com
[mailto:camunda-...@googlegroups.com] Im Auftrag von Falko Menge
Gesendet: Freitag, 13. Dezember 2013 14:23
An: camunda-...@googlegroups.com
Betreff: [camunda-bpm-users] history level cannot be changed

--
You received this message because you are subscribed to the Google Groups
"camunda BPM users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/camunda-bpm-users/52AB0A32.20803%40camun
da.com.
For more options, visit https://groups.google.com/groups/opt_out.

[cweber]

> IMHO you just have to make sure to adjust the flag in the database
>
> according to your processEngineConfiguration. If you adjust both
>
> everything works fine.
>

Hi,
I have a few questions about this history setting in the database.

1) Does that mean it is not possible to run the engine with to different configurations like a processEngine and a "noHistoryProcessEngine", for example?

My intention is that both should use the same database tables if possible but for a defined workflow the engine should not save the variables.

2) Why is there a config-setting like <property name="history">full</property> if the entry in the database really defines the level.

I got an error while trying to set the level in the application-context.xml because it is different to the setting in the database.

Am I not allowed to change this setting for my configuration?

3) What does schema.history mean? Kann I add there different history schema?

Thanks for help.

[Bernd Rücker (camunda)]

Hi Rob.

IMHO it is not possible to run the same database with different engine
configurations unless you overwrite this check. WHY it is there is hard to
answer - I think it is a heritage from Activiti. From my point of view it
would be cool to delete - but actually that�s a decision for the core team
(which is actually under heavy load the moment). So I think best is to
overwrite this in your own application (you will see the right location in
the code by locking at the stacktrace you get ;-)).

Cheers
Bernd
Consultant & Evangelist (www.camunda.org/community/team.html)
We are hiring: http://www.camunda.org/community/jobs.html

-----Urspr�ngliche Nachricht-----
Von: camunda-...@googlegroups.com

[mailto:camunda-...@googlegroups.com] Im Auftrag von cweber
Gesendet: Montag, 16. Dezember 2013 16:43
An: camunda-...@googlegroups.com
Betreff: Re: [camunda-bpm-users] history level cannot be changed

--
You received this message because you are subscribed to the Google Groups
"camunda BPM users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/camunda-bpm-users/f6bd7a87-ebd0-4c4b-99b
e-9e6d239139b6%40googlegroups.com.

[Daniel Meyer]

Hi,

we could add a switch to the configuration "historyLevelCheckEnabled". Default is "true", if set to false this check would not be performed.

Open for pull requests :)

Cheers,

Daniel

[Bernd Rücker (camunda)]

+1

And next step is changing the default to false J

--

You received this message because you are subscribed to the Google Groups "camunda BPM users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-users/d63655f7-061c-4814-aae3-87a20a6740b6%40googlegroups.com.

[Jan Galinski]

we could add a switch to the configuration "historyLevelCheckEnabled". Default is "true", if set to false this check would not be performed.

Thats exactly what I would need, see https://github.com/jangalinski/camunda-bpm-dropwizard/issues/7

Any news on this? 

[Jan Galinski]

I fixed my issue by allowing an additional historyLevel "auto" and in that case query act_ge_property for the current value.

See https://github.com/jangalinski/camunda-bpm-dropwizard/blob/master/core/src/main/java/org/camunda/bpm/extension/dropwizard/CamundaConfiguration.java  lines 60ff.