You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we try and run the TPCH query set in a sharded setup, we see that the first query -
select
l_returnflag,
l_linestatus,
sum(l_quantity) as sum_qty,
sum(l_extendedprice) as sum_base_price,
sum(l_extendedprice * (1- l_discount)) as sum_disc_price,
sum(l_extendedprice * (1- l_discount) * (1+ l_tax)) as sum_charge,
avg(l_quantity) as avg_qty,
avg(l_extendedprice) as avg_price,
avg(l_discount) as avg_disc,
count(*) as count_order
from
lineitem
where
l_shipdate <= date_sub('1998-12-01', interval 108 day)
group by
l_returnflag,
l_linestatus
order by
l_returnflag,
l_linestatus;
gives back incorrect fields for a bunch of columns, wherein the precision of the decimal fields doesn't match what mysql gives us.
Reproduction Steps
Create a sharded cluster with the following vschema -
Overview of the Issue
If we try and run the TPCH query set in a sharded setup, we see that the first query -
gives back incorrect fields for a bunch of columns, wherein the precision of the decimal fields doesn't match what mysql gives us.
Reproduction Steps
Create a sharded cluster with the following vschema -
and the following schema -
Binary Version
Operating System and Environment details
Log Fragments
No response
The text was updated successfully, but these errors were encountered: