Use Shell dispatching a kettle component for a large number of kettle jobs can cause a memory explosion. Can you support this aspect of scheduling optimization
@zhaxiaodong9860 is doing this feature
Each call to kettle with a shell script will Initialize a JVM environment, which is the reason of memory overload.Calling the kettle API with Java can solve the memory overload problem, and I'm currently planning to support kettle job/transformation in the DS.
Each call to kettle with a shell script will Initialize a JVM environment, which is the reason of memory overload.Calling the kettle API with Java can solve the memory overload problem, and I'm currently planning to support kettle job/transformation in the DS.
good job, if you have some progress for this feature, please add to the comment
@zhaxiaodong9860 this feature is done? I ask a question. where the ktr/kjb save? file or db?
@lzy305 Not yet,I plan to achieve both. It's planned to be finished by the end of May.
@lzy305 Not yet,I plan to achieve both. It's planned to be finished by the end of May.
Hi~ how is the progress
@zhaxiaodong9860 Hi ~ how is the progress
what kettle vision is supported and how is the progress?
@zhaxiaodong9860 hi ,how is the progress?
Most helpful comment
Each call to kettle with a shell script will Initialize a JVM environment, which is the reason of memory overload.Calling the kettle API with Java can solve the memory overload problem, and I'm currently planning to support kettle job/transformation in the DS.