Angelo Fausti

Is this in the InfluxDB 2 roadmap? It would help us to migrate from Chronograf to the InfluxDB 2 UI and use some of the new UI features - thanks.

Update on this issue: I tried to register the two URLs `/job/{job_id}` and `/job` defining two different endpoints explicitly, but it didn't work. ``` api.add_resource(Job, '/job', endpoint='job_without_arg') api.add_resource(Job, '/job/', endpoint='job_with_arg')...

btw, thanks for developing flasgger it is great to have the API spec as close as possible to the code. I'm also using the swagger specification extracted by flasgger to...

Hi @oceanicdev I am still using the work around described above. @rochacbruno I would be happy to contribute would you provide any guideline?

@adamchainz I would like to use django-mysql with MariaDB 10.2+ and query JSON fields, is it currently possible? thank you.

It would be great to have this PR merged in!

@xuzikun2003 In your example you would have too many measurements and only one field for each measurement in InfluxDB which is not a good [schema design](https://docs.influxdata.com/influxdb/v1.8/concepts/schema_and_data_layout/). Trying to make the...

Right, thanks for the clarification. My understanding from the [InfluxDB Sink documentation](https://docs.lenses.io/4.1/integrations/connectors/stream-reactor/sinks/influxsinkconnector/) is that the current version of the connector does not support nested fields in the payload schema.

However see also #329, if the name of the keys `key1`, `key2`, `key3` are fixed you could try a KSQL query like this: ``` connect.influx.kcql="INSERT INTO key1 SELECT key1.* FROM...

Thanks @davidsloan! Indeed I just tested the TIMESTAMPUNIT to specify the precision of the timestamp field and that worked, so I reverted the following: ``` @@ -72,7 +72,7 @@ object...