zhengyuan-cn commented on PR #4283:
URL: 
https://github.com/apache/incubator-seatunnel/pull/4283#issuecomment-1455784907

   > > hi, version 2.21 ,It's Happened NoSuchMethod when the dependency of 
influxdb-java's version 2.11 . downgraded version to 2.15 it works correct.
   > > exception detail: 23/02/27 10:50:06 INFO AbstractPluginDiscovery: Load 
plugin: PluginIdentifier{engineType='seatunnel', pluginType='source', 
pluginName='InfluxDB'} from classpath Exception in thread "main" 
java.lang.NoSuchMethodError: kotlin.collections.ArraysKt.copyInto([B[BIII)[B at 
shaded.okio.Segment.writeTo(Segment.kt:169) at 
shaded.okio.Segment.compact(Segment.kt:152) at 
shaded.okio.Buffer.write(Buffer.kt:1842) at 
shaded.okio.Buffer.read(Buffer.kt:1854) at 
shaded.okio.Buffer.writeAll(Buffer.kt:1642) at 
shaded.okio.Options$Companion.buildTrieRecursive(Options.kt:187) at 
shaded.okio.Options$Companion.buildTrieRecursive(Options.kt:174) at 
shaded.okio.Options$Companion.buildTrieRecursive$default(Options.kt:113) at 
shaded.okio.Options$Companion.of(Options.kt:72) at 
shaded.okhttp3.internal.Util.(Util.kt:71) at 
shaded.okhttp3.internal.concurrent.TaskRunner.(TaskRunner.kt:309) at 
shaded.okhttp3.ConnectionPool.(ConnectionPool.kt:41) at 
shaded.okhttp3.ConnectionPool.(ConnectionPoo
 l.kt:47) at shaded.okhttp3.OkHttpClient$Builder.(OkHttpClient.kt:471) at 
org.apache.seatunnel.connectors.seatunnel.influxdb.client.InfluxDBClient.getInfluxDB(InfluxDBClient.java:42)
 at 
org.apache.seatunnel.connectors.seatunnel.influxdb.source.InfluxDBSource.prepare(InfluxDBSource.java:84)
 at 
org.apache.seatunnel.core.starter.spark.execution.SourceExecuteProcessor.initializePlugins(SourceExecuteProcessor.java:88)
 at 
org.apache.seatunnel.core.starter.spark.execution.AbstractPluginExecuteProcessor.(AbstractPluginExecuteProcessor.java:49)
 at 
org.apache.seatunnel.core.starter.spark.execution.SourceExecuteProcessor.(SourceExecuteProcessor.java:51)
 at 
org.apache.seatunnel.core.starter.spark.execution.SparkExecution.(SparkExecution.java:50)
 at 
org.apache.seatunnel.core.starter.spark.command.SparkApiTaskExecuteCommand.execute(SparkApiTaskExecuteCommand.java:54)
 at org.apache.seatunnel.core.starter.Seatunnel.run(Seatunnel.java:39) at 
org.apache.seatunnel.core.starter.spark.SeatunnelSpark.main
 (SeatunnelSpark.java:34) at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498) at 
org.apache.spark.deploy.JavaMainApplication.start(SparkApplication.scala:52) at 
org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:855)
 at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:161) at 
org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:184) at 
org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:86) at 
org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:930) at 
org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:939) at 
org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
   > 
   > Are we use old api to access influxDB? Can we upgrade version and modify 
the way access influxDB?
   
   I use influxDB version 1.8.10,  seatunnel-influxDB  use simple config. as 
below
   `InfluxDB { 
       url="http://10.x.x.22:8086";
       database="data_storage"
       password="xxxxxx"
       sql="select temp3,time from lunzi where time >= '2023-01-11 16:18:00' 
and time < '2023-01-11 16:19:00' tz('Asia/Shanghai')"
       fields { 
                   temp3 = float
                   time = bigint
           } 
   
       result_table_name="source1"
   }`


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to