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
Hey there, had to observe the logs to understand that I can't count a jsonb value. In the meantime I can count(*), but not count(pv.*), pv being an alias for a mat view.
Error message/log
thread 'thread 'risingwave-streaming-actor' panicked at 'streaming agg state not implemented: Count
Jsonb Int64', src/stream/src/executor/aggregation/agg_impl/mod.rs:157:13
Regarding the panic on count(jsonb) in streaming (mat view), it would not be an issue after the refactor mentioned in #10752 (comment) . But we can also do a quick fix.
As for count(pv.*), it is equivalent to count(pv) and we would enhance our support as part of #9694. Before that you can use count(*) as long as there are no outer joins, or use count(pv.foo) when it is okay not to distinguish foo is null vs pv is not distinct from null during an outer join.
Describe the bug
Hey there, had to observe the logs to understand that I can't count a jsonb value. In the meantime I can
count(*)
, but notcount(pv.*)
,pv
being an alias for a mat view.Error message/log
To Reproduce
everything is reproducible at https://github.com/docteurklein/risingwave-demo
Expected behavior
I expected a better error message, and optionaly to be able to do that like in postgres.
How did you deploy RisingWave?
using docker-compose but with a single
playground
service`The version of RisingWave
select version(); -- PostgreSQL 8.3-RisingWave-1.0.0-alpha (2b6d7d6)
docker image: risingwavelabs/risingwave:nightly-20230709
Additional context
No response
The text was updated successfully, but these errors were encountered: