Discarding Data App jobs after consumer use

KNIME Business Hub
1

Hi, We’re currently migrating from the KNIME Server to the KNIME Business Hub.

Previously, at the last page of the KNIME Server’s WebPortal a ‘discard’ button would appear which would enable the consumer of the data app to click ‘discard’ when they’re finished, thereby closing the window and discarding the associated job on the KNIME Server.

On the Business Hub’s Data Apps Portal there is no such ‘discard’ button. Is there a way to discard the associated job once the consumer has finished with it (e.g. when they close the associated window)?

I’ve noticed (and tried) the ‘Edit data app->Advanced settings–>job lifecycle–> discard upon successful execution’, but this option discards the data app as soon as the consumer reaches the final page of the data app - without allowing them to view the last page…

Any advice would be much appreciated!

Thanks,

Mike

1 Like
2

Hi Mike,

We are currently working on this feature to improve the user experience.

Until the new implementation is available we recommend to proceed as follows:

Don’t use Edit data app->Advanced settings–>job lifecycle–> discard upon successful execution as this would cause the interactive DataApp to be closed too early.

Instead please configure the “maxJobTimeInMemory” as well as the “maxJobLifeTime” to a low time span as described here.

Best,
Micha

3

Hi Micha,

Thanks for your reply and advice. I look forward to the new feature. Until this is available I have changed the maxJobTimeInMemory and maxJobLifeTime for the execution context. Upon saving a green confirmation appears stating ‘Execution context updated’, but upon checking the execution context’s settings again I can see that it has reverted back to its original setting…Any idea what this is happening…?
Thanks,
Mike

4

Hi Mike,

Could you please check, which of these options was reverted to its default? Or were both configurations reset to their respective defaults?

Thanks, Micha

5

Hi Mike,

A quick update: I just found out that this is a bug on our side not showing the right configured time for the macJobLifeTime, while the setting is applied properly. We have already a development ticket open to fix this (internal reference HUB-8903).

Just for the clarification: The set time is configured properly by pressing on saving, only the GUI does not reflect the made change.

I am sorry for the inconvenience caused.

Best, Micha

2 Likes