[fix](jni)fix jni use timezone_obj get timezone be core. (#41956) #42070
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.
bp #41956
This PR #40225 try to pass time zone info from BE to JNI, and it use
_state->timezone_obj().name()
to get the timezone name.
But when we do some rolling upgrade of BE, it may coredump like:
This PR use another method:
_state->timezone()
, which just return a string, instead of reading and initializingtime zone info file, to avoid potential coredump.