SQL query error on D102

When I try to run the query on VM env. It will generate the error about “Serialization is only allowed for SelectionVectorMode.NONE. This was in SelectionVectorMode.TWO_BYTE”

SQL:
SELECT payment_type, COUNT() AS C
FROM “taxi WIP”.“sample_data”
WHERE trip_distance > 1 AND
passenger_count < 5
GROUP BY payment_type
HAVING COUNT(
) > 1000
ORDER BY COUNT(*) DESCc460d8a8-b873-453b-8a1f-68ec09c33451.zip (11.6 KB)

3 Likes

Any updates regarding this issue?
7db9c1e9-b236-4355-844e-18fe4065b8eb.zip (12,5 KB)

From Dremio Jobs section, everything seems OK but it’s not.

Regards
Rosario

@0iras0r

Where do you see this error?

Reflection Course D102 " Introducing the concept of Substitution"
@balaji.ramaswamy
Thanks in advance.
Rosario

It seem to have problems in the ORDER BY COUNT(*) ASC

Hi @balaji.ramaswamy,
did you reproduce the issue?

UPDATE: if I do this SQL query, I think it works, but I want to understand why.
SELECT day_of_month, C
FROM (
SELECT DATE_PART(‘day’,pickup_datetime) AS day_of_month, COUNT(*) AS C
FROM “Reflections Lab (WIP)”.trips
WHERE vendor_id = ‘VTS’ AND
trip_distance > 1 AND
passenger_count < 5
GROUP BY DATE_PART(‘day’, pickup_datetime)
HAVING C > 150000
) nested_0
ORDER BY C DESC

Thanks in advance,
Rosario

@0iras0r

We were able to reproduce the issue. Will keep you posted on the fix

Thanks
@balaji.ramaswamy

I get the same error even with this modified query.

Hi Balaji, any updates regarding these issue?

This is still happening. Seems to happen on any query with a HAVING and ORDER BY clause.

1 Like

Well for me this was solved by clicking join by mistake, then cancel and re-running the query… Ups i guess

1 Like

It’s not clear why this resolves it, but it works now.

removing the ORDER BY clause fixes this issue for me.