0.21.0

Bug Fixes

1. #234: Add support for connecting to InfluxDB servers using IPv6 addresses.
   • IPv6 addresses in server URLs must be enclosed in square brackets, for example, http://[2001:db8::1]:8086.
   • IPv6 zone identifiers are not currently supported.

Breaking Changes

1. #217: Makes the writing API simpler and more consistent with other v3 clients.

   • Removes unused InfluxLoggingHandler class.
   • WriteApi now handles all functions to write to InfluxDB.
     • The following internal classes have been removed:
       • Configuration
       • ApiClient
       • WriteService
       • InfluxDBClient
     • The following internal classes have been refactored:
       • write_client._sync.RestClient - this class is now responsible for low-level handling of transport requests. End users should not need to use it directly.
       • write_client.client.WriteApi - all internal settings needed for writing are now encapsulated within this Api.
   • Refactors Multiprocessing helper class.
   • Migration Guidance
     • InfluxDBClient3 constructor now has additional parameters for configuring the internal WriteApi and RestClient.
       • auth_scheme - string - the token authentation scheme, typically Token or Bearer.
       • enable_gzip - boolean - whether or not to compress data in writing payloads.
       • gzip_threshold - int - minimum payload size to trigger gzip compression when enable_gzip is True.
       • point_settings - PointSettings - default settings used when writing Points, primarily used to wrap default tags to be added to Point data.
       • debug - boolean - toggle debug level logging.
     • Any clients explicitly using the Configuration, ApiClient, WriteService or legacy InfluxDBClient classes, will need to migrate their settings to the InfluxDBClient3 constructor.

2. #222: Refactor MultiprocessingWriter class.

   • New Process will be created by using DefaultContext.Process(target) to prevent erratic crashes, handle cross-platform code behavior safely, and coordinate complex resource sharing.
   • Users can now choose one of the start methods fork, spawn or forkserver when creating new Process. The default will be spawn.
   • Users can set time to live for the child process through process_ttl parameter, the default value will be 300 seconds.