-
Notifications
You must be signed in to change notification settings - Fork 68
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
[BUG] DQL/KQL queries gives results in Discover but not in csv reports #190
Comments
Root cause:When Reporting csv logic handles filters in the form of DQL/KQL queries, it is using esb.queryStringQuery() to build query, which takes in a Ref: Solution: TODO |
Currenly there's a OSD utility method I tied an implenetation like this, and the
I am thinking in the future is there a chance of not using elastic-builder? I don't think that's maintained by Opensearch, and was not created originally by Elastic either @joshuali925 @davidcui1225 @anirudha any thought? |
esb doesn't support constructing from JSON (author provided some workarounds in sudo-suhas/elastic-builder issue 28). I think we can only either parse FYI trace-analytics' filter DSL is directly built in JSON. It doesn't support everything in discover filter and has many TA specific stuff, but reporting could do something similar. Not sure if it's a better approach though, need to check how Dashboards converts filters to DSL |
Describe the bug
@zhongnansu
in the Discover query bar using DQL, if it's not strictly using the uppercase, or double quotes, even tho it gives results on Discover, but reports will be empty.
Example
both
geoip.city_name:"New York" AND geoip.continent_name: "North America"
and
geoip.city_name:New York and geoip.continent_name: North America
give same results on Discover, but the latter generate empty csv report.
The text was updated successfully, but these errors were encountered: