Datahub needs to be restarted on create-drop with every handler java class changes

[rahulverma94]

Hi Experts,

Every time we make changes to any handler class or write new handler class, the changes do not reflect on server till we restart Datahub on create-drop mode.

This is not a desired behaviour for a production , especially when you will always need to initialize datahub with prequisite sets of data like CHRMAS-CLASMAS and initial data load from hybris every time after create-drop restart.

We are on Hybris 6.7 and Datahub 6.7. Does SAP have any solution to handle this behaviour so that we can get away with create-drop mode restart?

[Slava]

Rahul,

Data Hub does not have a capability to load extensions with code customizations dynamically. So, unfortunately restart is required whenever code changes. However, this restart does not have to be create-drop as far as I know. Any autoInitMode should work, including 'ignore', unless there are model changes besides the code changes and the code relies on those changes.

Have you tried to restart in, let's say, 'ignore' mode?

[Former Member]

, for just java changes create-drop mode is not needed but if there is any change in composition layer or transformation expression changes then create-drop mode is needed.

[rahulverma94]

This is a big limitation when we need to restart data hub on create-drop for any composition handler or publication handler changes to reflect. The code changes do not reflect unless we restart on create-drop. I am sure on this.

[former_member333910]

Hi , as mentioned changes in custom Java code in your extensions shouldn't require a restart in create-drop mode in order for the changes to be reflected. I'm assuming you are running on standalone Tomcat. How are you deploying your custom Java code changes? I wonder if somehow something about the deploy process could be relevant to this issue.