-
Notifications
You must be signed in to change notification settings - Fork 35
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
CSV reports missing the Time field [BUG] #335
Comments
We saw the same with latest versions and also opened a ticket here. Have you found any workaround or root cause ? |
Facing the same issue with version 2.13.0. |
In lastest version the same. |
I'm using v 2.13.0 in AWS, I'm also facing same issue. |
Has a solution or workaround been shared? This is the closest forum to trying to figure out why dates are not being exported in the CSV. |
Is any progress to this issue? It is somehow strange that issue exists at least since 7 months and no reaction |
for now please see if this workaround works opensearch-project/reporting#668 (comment) |
We are also experiencing this issue as well |
Hi @joshuali925 and others (@TackAdam , @Swiddis , @rupal-bq -- to name a few contributors): I hope you folks can devote some attention to this bug. Including Their experience with Dashboards has been largely positive, but asking them to open Web Developer and edit the POST request feels almost cruel, and doesn't reflect well on the other lovely features you've built here. I'm not at all experienced with Typescript, but I'll try my best to submit a PR if that will help this work along. Thanks and Happy Holidays! |
What is the bug?
When exporting from discover I would expect the Time field column is missing from the report
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
The Time field should also be present
What is your host/environment?
Do you have any screenshots?
NA
Do you have any additional context?
I'm not sure if this is expected but it's been like this since the beginning
The text was updated successfully, but these errors were encountered: