Migrating same name fields from a measurement about outflux HOT 3 CLOSED

Yes, this is one of the cases we have trouble with. But I like the suggestion to 'promote' the field during migration. We'll discuss with the team and let you know our progress.

Thank you.

Will update the documentation for now that this is a limitation.

from outflux.

We merged a fix for this.
If you want to enable integer to float 'promotion' you need to explicitly specify the multishard-int-float-cast flag. This way if a field is discovered with both an integer and float type, it will promote it. But for any other types it will return an error. The explicit flag is required because integers in InfluxDB are int64, and floats are float64, and not all values of a int64 are supported by a float64

from outflux.

Hi Stephan - I believe this is actually one of the cases we don't support. @blagojts correct me if I'm wrong? Also, perhaps we should document the known limitations here + workarounds if they exist. cc @bboule

from outflux.