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
I had same problem with v2.6.1. There was integer/double type change of value field which was unnoticed.
The only workaround was to export data, clean table and import it back.
I had same problem with v2.6.1. There was integer/double type change of value field which was unnoticed. The only workaround was to export data, clean table and import it back.
Hi @latonita How did you exactly clean the data? and also how did you export and import it ?
@faiz-hcs I was using influxdb ui.
I have identified few records with wrong data type,
just saved those values on a paper and deleted it from the DB with CLI,
then I made a query in Data Explorer which returns all the data and saved to csv with 'save to csv' :) button
then added missing records to CSV file
then uploaded CSV with "Load data" section
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Link to issue on Influx forum :
https://community.influxdata.com/t/flux-query-does-not-return-results-if-wider-time-range-is-selected/33750/9
Environment info:
Config:
Default config.
Logs:
No error messages in the Logs as well as flux query logs.
The text was updated successfully, but these errors were encountered: