[CH-367] fix CH will continue to execute after JNI call fail #368
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Refactor releasing process
Simplify strip for new packages
…l_flag Resurrect build hash
…ash_v2 One more try to resurrect build hash
New package clickhouse-keeper
Docker release and regular builds
Fix automatic bucket prefix for master
…id IPv6, IPv4 values
…ease Backport release to 22.3
Backport ClickHouse#35799 to 22.3: Fix extract function parser
Backport ClickHouse#35733 to 22.3: Added settings for insert of invalid IPv6, IPv4 values
Backport ClickHouse#35820 to 22.3: Avoid processing per-column TTL multiple times
- Allow define version as file - Add inline cache - Fix auto_release_type function
Support full join with join condition Co-authored-by: shuai.li <shuai.li@kyligence.io>
Support Decimal type in Gluten Co-authored-by: shuai.li <shuai.li@kyligence.io>
…like Column 'deviceid' is not presented in input data (Kyligence#388)
Co-authored-by: shuai.li <shuai.li@kyligence.io>
…voking of JNI_Onload and finalized once at exit (Kyligence#377)
Co-authored-by: shuai.li <shuai.li@kyligence.io>
|
test this please |
liuneng1994
reviewed
Apr 10, 2023
| const char *nmsg = (env)->GetStringUTFChars(jmsg, NULL);\ | ||
| std::string msg = std::string(nmsg);\ | ||
| env->ReleaseStringUTFChars(jmsg, nmsg);\ | ||
| throw DB::Exception(DB::ErrorCodes::LOGICAL_ERROR, msg);\ |
There was a problem hiding this comment.
done, It's a little strange that It can compile pass without define it external in my local machine.
Co-authored-by: Robert Schulze <robert@clickhouse.com>
liuneng1994
reviewed
Apr 12, 2023
utils/local-engine/jni/jni_common.h
Outdated
| (env)->ExceptionClear();\ | ||
| jclass cls = (env)->GetObjectClass(excp); \ | ||
| jmethodID mid = env->GetMethodID(cls, "toString","()Ljava/lang/String;");\ | ||
| jstring jmsg = static_case<jstring>((env)->CallObjectMethod(excp, mid));\ |
liuneng1994
force-pushed
the
clickhouse_backend
branch
from
6528ff0
to
52be833
Compare
lwz9103
force-pushed
the
clickhouse_backend
branch
2 times, most recently
from
dc60d55
to
8066113
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
This pr fix the problem invoked by #305 , if don't throw CH exception, CH will continue to execute after JNI call failed. So it should throw a Clickhouse Exception with the JNI exception message so the root cause will be shown in spark.
It close #367 .