You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a csv file containing a column with dates, the date is being converted into a string.
When using the transformation to convert the field type to time, the time and date are always the same and do not match the source file.
@supilee please add one or more appropriate labels. Here are some tips:
if you are making an issue, TODO, or reminder for yourself or your team, please add one label that best describes the product or feature area. Please also add the issue to your project board. 🚀
if you are making an issue for any other reason (docs typo, you found a bug, etc), please add at least one label that best describes the product or feature that you are discussing (e.g. area/alerting, datasource/loki, type/docs, type/bug, etc). Our issue triage doc also provides additional guidance on labeling. 🚀
The "date" shown in the first table is a simple integer. Simple integers are interpreted as milliseconds since start of Unix epoch (1st of January, 1970 UTC). Due to your timezone this is 31st of December, 1969 at 4pm. So the field type conversion works as expected.
The question is, why is "2021-12-09" in the CSV converted to 44539?
When adding a csv file containing a column with dates, the date is being converted into a string.
When using the transformation to convert the field type to time, the time and date are always the same and do not match the source file.
DnD-TimeSample.csv
The text was updated successfully, but these errors were encountered: