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
Error on writePoint #66
Comments
Changing data types in influxdb is no good idea because they are "pinned" for each shard as soon as the first value is written. Plese check which value is really in the DB ... I think admin could show some values wrong (and influxdb do not support null at all, so value can not be null). Also please try latest version (or which version you use?) |
I understand that this is not a good idea, but I had to change the object that is linked to the original one. and there the type changed. I would not like to rewrite it in all scripts where it is used. driver version latest 1.8.4 |
But in fact according to your log the adapter did fine, he detected that type difference and fixed it and wrote it with the expected type. So only Admin seems to display wrong values in the table. Please check in DB directly what values are stored. Is it correct there? |
Try to select raw values plase ... not a "mean" |
there is no such function (raw). there are only these. I made an export, I attach the file. |
SELECT * from name ORDER BY time desc LIMIT 100 or such? |
Sorry bug yes this query makes no sense :-( |
I give up. created a new object and reassigned the associated object to it. |
if the object was a logical value and then became a number, I get this error. changing to other types does not produce results. null is written to the log.
influxdb_log.txt
The text was updated successfully, but these errors were encountered: