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
Null key in timeseries result for hyperUnique on missing columns #3625
Comments
I think I can fix this as part of #3572 since the underlying cause of the null key is that |
gianm
added a commit
to gianm/druid
that referenced
this issue
Oct 31, 2016
Also add SchemaEvolutionTest to help test this kind of thing. Fixes apache#3627 and includes test for apache#3625.
fjy
pushed a commit
that referenced
this issue
Nov 1, 2016
fundead
pushed a commit
to fundead/druid
that referenced
this issue
Dec 7, 2016
Also add SchemaEvolutionTest to help test this kind of thing. Fixes apache#3627 and includes test for apache#3625.
dgolitsyn
pushed a commit
to metamx/druid
that referenced
this issue
Feb 14, 2017
Also add SchemaEvolutionTest to help test this kind of thing. Fixes apache#3627 and includes test for apache#3625.
seoeun25
pushed a commit
to seoeun25/incubator-druid
that referenced
this issue
Feb 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the column for a hyperUnique aggregator doesn't exist, a null key appears in the TimeseriesResultValue. If results get combined by TimeseriesBinaryFn, these null keys get filtered out. But if results don't get combined (possibly because only one segment matched the query) then the query fails with a Jackson exception when it tries to serialize the null key, because null keys aren't allowed in JSON.
The text was updated successfully, but these errors were encountered: