gianm commented on issue #17821:
URL: https://github.com/apache/druid/issues/17821#issuecomment-2776520522
I tried to repro this and wasn't able to. It is possible it's been fixed
since Druid 31.0.0. There have been changes in the area of vectorized
expressions since then.
Here is what I did:
1. Populated `error-state` with `errorCode`
```
REPLACE INTO "error-state"
OVERWRITE ALL
SELECT * FROM (VALUES ('1'), ('2')) t (errorCode)
PARTITIONED BY ALL
```
2. Populated `help-state` with `helpCode`
```
REPLACE INTO "help-state"
OVERWRITE ALL
SELECT * FROM (VALUES ('3'), ('4')) t (helpCode)
PARTITIONED BY ALL
```
3. Ran this query (same as yours, but with a broader time interval, since
the datasets I inserted would use the default timestamp `1970-01-01`)
```json
{
"queryType": "groupBy",
"dataSource": {
"type": "union",
"dataSources": [ "error-state", "help-state" ]
},
"dimensions": [ "code" ],
"granularity": "all",
"virtualColumns": [
{
"type": "expression",
"name": "code",
"expression": "nvl(errorCode, helpCode)",
"outputType": "STRING"
}
],
"intervals": [ "0000/3000" ],
"context": {"vectorize": true}
}
```
I got good results:
```
{"code":"1"}
{"code":"2"}
{"code":"3"}
{"code":"4"}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org
For additional commands, e-mail: commits-h...@druid.apache.org
