-
Notifications
You must be signed in to change notification settings - Fork 203
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
A fixed result is obtained when executing query sql if the real data is bigger than fixed result #1268
Comments
I found the reason of this question, Because I have created two tables both with column |
Could you please share the table schema including the table type. (ROW or COLUMN)? Also, I see that you are using very old version(0.8) of the product. Could you please confirm if it is seen in latest version too? |
These tables are both row table,and there is currently no way to test the latest version。 |
When querying a table in snappydata cluster through snappysession remotely,like,
select sum(COL_A)/count(1) AS RATE, sum(COL_A) AS NUM , COL_B FROM TABLE_A GROUP BY COL_B
,if the expected and right result is
(100,10000,NN)
, the real result obtained by executing sql remotely is(100,3072,NN)
,but it can be right by executing sql with using the SnappyData SQL Shell in snappydata cluster directly.So far,when other sqls that only querying one target like
select sum(COL_D) AS NUM , COL_B FROM TABLE_B GROUP BY COL_B
, this problem has never happened.If I only restart the cluster without any other operations , the problem is still there.
If I cleaned the work Directory in lead of snappydata cluster and restart the cluster, the problem is resolved, but it will be repeated in few days.
When the problem arises, if I change
group by COL_B
togroup by COL_C
,the result is right. if I only queryselect sum(COL_A) AS NUM , COL_B FROM TABLE_NAME GROUP BY COL_B
,the result is still wrong.I checked all settings of the cluster, there is not any cache related configuration.
please help me to solve this problem!
PS: The version I used is v0.8
The text was updated successfully, but these errors were encountered: