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
The map implementation no longer converts empty characters, after the update from 0.20.0 to 0.20.1 #10859
Comments
For the person looking in to this - it appears there was a similar problem raised with this type of extraction function in #4301 - I didn't dig enough to know if they're related, but I thought I'd just link them. It would probably be good to add an integration test to the query tests as part of this bug fix. |
You are right this is caused by ae4b192#diff-a6471b0e75ec5f881cceafb6186%5B%E2%80%A6%5De04e6fe4e8a1fca21674bf9a5R64-R112 It seems like annotated org.apache.druid.query.extraction.MapLookupExtractor is a subclass of com.fasterxml.jackson.databind.introspect.AnnotatedClass and expression |
@odajun Thanks for filing this bug. can you answer few questions
|
@abhishekagarwal87 Thanks for checking.
We don't set this property.
|
The map implementation no longer converts empty characters, after the update from 0.20.0 to 0.20.1
Affected Version
0.20.1
Description
In our environment, the results of the following queries changed before and after the upgrade.
expected result
actual result
We think the cause is known to be due to the following update.
ae4b192#diff-a6471b0e75ec5f881cceafb6186%5B%E2%80%A6%5De04e6fe4e8a1fca21674bf9a5R64-R112
The text was updated successfully, but these errors were encountered: