lynnmatrix opened a new pull request #6601: ISSUE-6514 Add support for 
influxdb2 in pulsar-influxdb-sink(#6514)
   Fixes #6514
   ### Motivation
   The latest InfluxDB release(v2) has changed their write path, 
'org'、'bucket'、'token' are required properties to communicate with it; New 
InfluxDB client library is provided with different package name, from 
org.influxdb to com.influxdb
   This PR would add support to the latest InfluxDB 2.0 write API.
   ### Modifications
   Since the influxdb2 client library changes a lot, even the package name 
changed, so the new client library is added in this pull request, while the old 
one is kept, which means the implement of client v1 is kept unchanged, so no 
migration is needed for influxdbv1 users。
   The sink for influxdbv1 fails to decode  messages encoded in json, it 
supposes only avro. Support of json schema is added in this pull request.
   The sink for influxdbv1 requires  influxdb fields as schema fields, so users 
should define schemas for each kind of device, that is not convenient.  The new 
added sink for influxdbv2 redefines the message schema, and wraps influxdb 
'fields' in one map field, just like 'tags' which is already defined as map in 
the previous sink for influxdbv1.
   ### Verifying this change
     - Unit tests are added for this sink for influxdbv2.
   ### Does this pull request potentially affect one of the following parts:
     - **Dependencies (does it add or upgrade a dependency): yes**
     - The public API:  no
     - The schema: no
     - The default values of configurations: no
     - The wire protocol: no
     - The rest endpoints:  no
     - The admin cli options: no
     - Anything that affects deployment: no
   ### Documentation
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? docs

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to