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
q='''let now = now();let T = datatable(start:datetime, end:datetime) [ datetime(2023-02-10T00:00:00.000000000+00:00), datetime(2023-02-11T00:00:00.327242700+00:00), datetime(2023-02-10T00:00:00.000000000+00:00), datetime(2023-02-11T00:00:00.000000000+00:00),];T| extend delta = end - start'''%kqltest_df<<-auto_dataframe=True-queryqtest_df
Problem description
When the timestamp has sub-second precision as per the above code example's first table row, it causes the conversion to a pandas data-frame to have an incorrect timedelta. E.g. it resulted in 38 days 21:00:27 instead of the correct detla of 1 days 0:00:00.32724700. When run in Log Analytics, the timespan value returned was 1.00:00:00.3272427. So it seems like there is some timespan -> timedelta conversion issue when sub-second precision occurs.
Interestingly, this problem does not manifest if the timespan did not inlcude sub-second precision values as per the second row in the example table.
If query related, does it happen on other platforms (Kusto Web UI, Kusto Explorer, Log Analytics in Azure Monitor)?
No, Log Analytics returns expected timespan values.
Output of pip freeze and %kql --bugreport
[bugreport must be executed immediatly after bug noticed]
Code Sample, a copy-pastable example if possible
Problem description
When the timestamp has sub-second precision as per the above code example's first table row, it causes the conversion to a pandas data-frame to have an incorrect timedelta. E.g. it resulted in
38 days 21:00:27
instead of the correct detla of1 days 0:00:00.32724700
. When run in Log Analytics, the timespan value returned was1.00:00:00.3272427
. So it seems like there is some timespan -> timedelta conversion issue when sub-second precision occurs.Interestingly, this problem does not manifest if the timespan did not inlcude sub-second precision values as per the second row in the example table.
If query related, does it happen on other platforms (Kusto Web UI, Kusto Explorer, Log Analytics in Azure Monitor)?
No, Log Analytics returns expected timespan values.
Output of
pip freeze
and%kql --bugreport
[bugreport must be executed immediatly after bug noticed]
[paste the output of
pip freeze
here below this line]The text was updated successfully, but these errors were encountered: