[Feature][Connector-V2] Add influxDB connector source

[531651225]

Purpose of this pull request

#1946
Add InfluxDB Connector Source
close #2595

Check list

• Code changed are covered with tests, or it does not need tests for reason:
• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

[hailin0]

can you add e2e-testcase(spark)?

[531651225]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector.
At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

[EricJoy2048]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

[CalvinKirs]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

We'd better be able to rename these jars @TyrantLucifer WDYT?

[TyrantLucifer]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

We'd better be able to rename these jars @TyrantLucifer WDYT?

Yes, aggre with @CalvinKirs , you can add maven-shade plugin in your pom to rename these jars. BTW, could you please use httpclient, not use okhttp, it's better to unify versions and dependencies for http dependencies. In subsequent iterations, we need to abstract this http-related functionality into public modules and replace them uniformly with the renamed httpclient. What do you think about? @531651225 @CalvinKirs

[531651225]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

We'd better be able to rename these jars @TyrantLucifer WDYT?

Yes, aggre with @CalvinKirs , you can add maven-shade plugin in your pom to rename these jars. BTW, could you please use httpclient, not use okhttp, it's better to unify versions and dependencies for http dependencies. In subsequent iterations, we need to abstract this http-related functionality into public modules and replace them uniformly with the renamed httpclient. What do you think about? @531651225 @CalvinKirs

It seems impossible to replace okhttp with httpclient. The okhttp jar is used internally by the influxdb-java.jar.
Influxdb-java is the only way officially provided for accessing influxdb.

[TyrantLucifer]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

We'd better be able to rename these jars @TyrantLucifer WDYT?

Yes, aggre with @CalvinKirs , you can add maven-shade plugin in your pom to rename these jars. BTW, could you please use httpclient, not use okhttp, it's better to unify versions and dependencies for http dependencies. In subsequent iterations, we need to abstract this http-related functionality into public modules and replace them uniformly with the renamed httpclient. What do you think about? @531651225 @CalvinKirs

It seems impossible to replace okhttp with httpclient. The okhttp jar is used internally by the influxdb-java.jar. Influxdb-java is the only way officially provided for accessing influxdb.

This is really bad news. But don't worry, we also have the ultimate weapon, the maven-shade plugin. We can use this plugin to rename packages of okhttp to avoid jar conflict.

[531651225]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

We'd better be able to rename these jars @TyrantLucifer WDYT?

Yes, aggre with @CalvinKirs , you can add maven-shade plugin in your pom to rename these jars. BTW, could you please use httpclient, not use okhttp, it's better to unify versions and dependencies for http dependencies. In subsequent iterations, we need to abstract this http-related functionality into public modules and replace them uniformly with the renamed httpclient. What do you think about? @531651225 @CalvinKirs

It seems impossible to replace okhttp with httpclient. The okhttp jar is used internally by the influxdb-java.jar. Influxdb-java is the only way officially provided for accessing influxdb.

This is really bad news. But don't worry, we also have the ultimate weapon, the maven-shade plugin. We can use this plugin to rename packages of okhttp to avoid jar conflict.

Thanks for your advice. I'll try. By the way, is there any other case where the shade plugin is used by other connectors

[TyrantLucifer]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

We'd better be able to rename these jars @TyrantLucifer WDYT?

Yes, aggre with @CalvinKirs , you can add maven-shade plugin in your pom to rename these jars. BTW, could you please use httpclient, not use okhttp, it's better to unify versions and dependencies for http dependencies. In subsequent iterations, we need to abstract this http-related functionality into public modules and replace them uniformly with the renamed httpclient. What do you think about? @531651225 @CalvinKirs

It seems impossible to replace okhttp with httpclient. The okhttp jar is used internally by the influxdb-java.jar. Influxdb-java is the only way officially provided for accessing influxdb.

This is really bad news. But don't worry, we also have the ultimate weapon, the maven-shade plugin. We can use this plugin to rename packages of okhttp to avoid jar conflict.

Thanks for your advice. I'll try. By the way, is there any other case where the shade plugin is used by other connectors

You can refer to https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html or see seatunnel-config module get the usage of shade plugin.

[531651225]

can you add e2e-testcase(spark)?

there is a conflict of the okhttp jar between the Spark jar and the influxdb connector. At present, this problem is solved by specifying the replacement of conflicting packages in the spark jars directory in the document

@CalvinKirs PTAL

We'd better be able to rename these jars @TyrantLucifer WDYT?

Yes, aggre with @CalvinKirs , you can add maven-shade plugin in your pom to rename these jars. BTW, could you please use httpclient, not use okhttp, it's better to unify versions and dependencies for http dependencies. In subsequent iterations, we need to abstract this http-related functionality into public modules and replace them uniformly with the renamed httpclient. What do you think about? @531651225 @CalvinKirs

It seems impossible to replace okhttp with httpclient. The okhttp jar is used internally by the influxdb-java.jar. Influxdb-java is the only way officially provided for accessing influxdb.

This is really bad news. But don't worry, we also have the ultimate weapon, the maven-shade plugin. We can use this plugin to rename packages of okhttp to avoid jar conflict.

Thanks for your advice. I'll try. By the way, is there any other case where the shade plugin is used by other connectors

You can refer to https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html or see seatunnel-config module get the usage of shade plugin.

thks, The conflict has been resolved.
have already added spark E2E, Please help review @hailin0 @CalvinKirs @EricJoy2048 @TyrantLucifer

[EricJoy2048]

@531651225 does this pr can review again?
If it's ok,@hailin0 @TyrantLucifer @Hisoka-X please reviews this pr again.

[531651225]

@531651225 does this pr can review again? If it's ok,@hailin0 @TyrantLucifer @Hisoka-X please reviews this pr again.

@531651225 does this pr can review again? If it's ok,@hailin0 @TyrantLucifer @Hisoka-X please reviews this pr again.

Okay, help me review, thks

[hailin0]

LGTM

[ashulin]

Please add split snapshot.
you can see https://github.com/apache/incubator-seatunnel/blob/dev/seatunnel-connectors-v2/connector-iotdb/src/main/java/org/apache/seatunnel/connectors/seatunnel/iotdb/source/IoTDBSourceReader.java

[531651225]

Please add split snapshot. you can see https://github.com/apache/incubator-seatunnel/blob/dev/seatunnel-connectors-v2/connector-iotdb/src/main/java/org/apache/seatunnel/connectors/seatunnel/iotdb/source/IoTDBSourceReader.java

already fixed

[EricJoy2048]

@ashulin @hailin0 PTAL

[ashulin]

LGTM

[EricJoy2048]

+1