Closed erlfos closed 5 years ago
Thank you for trying out Outflux. Can you show us how you passed the flags when starting the tool? (No need for connection stuff, just measurement name and other options) :)
I run Outflux in a TimescaleDB docker container with this command:
bash-4.4# ./outflux schema-transfer --input-server http://influxdb:8086 spgw --output-conn="dbname=spgw user=postgres"
Confirmed, there is trouble when having dots in the measure name. You can sidestep it by using quotes and adding the autogen retention policy, but TimescaleDB/Postgres ends up trying to create a schema with the first part of the measure name (this case schema VS, table AsrRxMalformedPkts). Will issue a bugfix and then do another release. Thank you for reporting it
@erlfos We have a fix for this issue in #60 . In the same PR we add explicit support for retention policies, but we also fixed the bug where the dot in the measurement name is interpreted as a RP. You can try out the code from the PR to confirm that it's been fixed. After our checks pass we'll merge it in master and in a few days issue a new release
Hi
I am testing Outflux to see if Timescale can offer an alternative to InfluxDB, but our measurements in InfluxDB often have dots in the measurement name (example: VS.AsrRxMalformedPkts) and this causes Outflux to fail. Outflux translates "VS" as the retention policy and "AsrRxMalformedPkts" as the measurement name, and the resulting query fails:
Here is the output from Influx:
If there is a dot in the measurement name the query will have to be like this: SHOW FIELD KEYS FROM "VS.AsrRxMalformedPkts"