-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different result between origin Spark and Blaze #675
Comments
can you also provide the schema and sample data of table |
Sorry for forgetting the important information. CREATE TABLE blaze_t.test_level (
id INT,
name STRING,
code STRING,
parent_code STRING,
vender_id INT,
parent_id INT,
level INT,
status INT,
classifylist STRING,
type INT,
shop_type INT,
applier STRING,
created STRING,
reviser STRING,
modified STRING,
yn INT,
log_info_json STRING,
cm_code STRING,
rb_code STRING,
main_cm_code STRING,
main_rb_code STRING)
stored as parquet;
and the sample data is in this link: |
This issue is stale because it has been open for 30 days with no activity. |
Did you also forget to upload the sample data for Table |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When execute the SQL, origin Spark and Blaze will get different value.
To Reproduce
Steps to reproduce the behavior:
[TABLE] blaze_t.test_level's DATA is in output.csv file.
output.csv
[ENV]
Executor: 4executors1core, memory: 2g, overhead memory: 4g
Driver: 2g
use celeborn v0.5.1 to solve shuffle data
Spark v3.3.4 in k8s
Expected behavior
Hoping they can get the same result.
Screenshots
origin Spark:
Blaze:
The text was updated successfully, but these errors were encountered: