[WIP] fix: fix the dataload with cronJob failure in jindoCacheRuntime #4359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Ⅰ. Describe what this PR does
In the upgrade of historical versions of jindocache fuse, the referenced configuration file path changed. Therefore, in PR#3662 the contributor modified the configuration path for jindocache in the dataload job helm template. However, this modification did not take into account the cronJob. As a result, when using jindoCache as a runtime in Fluid versions v1.0.0 to v1.0.3, the dataload cronJob ends up referencing an incorrect configuration file path, leading to failure.
Ⅱ. Does this pull request fix one issue?
fixes #4357