You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
客户端提交任务到集群,报错 source 的connector 的jar 包 class not found
When the client submits a task to the cluster, an error message is displayed: 【com.hazelcast.nio.serialization.HazelcastSerializatcionException: java.lang.ClassNotFoundException: orgg.apache.seatunnel.connectors.seatunnel.feishu.source.Feishusource】
由于启动的 client 的 SEATUNNEL_HOME 目录是本地的,然后本地启动cluster,提交成功!
Since the SEATUNNEL_HOME directory of the started client is local, and then the cluster is started locally, the submission is successful!
最后发现原因是client提交的任务,SEATUNNEL_HOME 是需要与 cluster 中的保持一致。
Finally, I found that the reason was the task submitted by the client. SEATUNNEL_HOME needs to be consistent with that in the cluster.
除了使用 REST 提交,有没有任何可以解决的办法呢?
Is there any solution besides using REST submission?
Search before asking
What happened
客户端提交任务到集群,报错 source 的connector 的jar 包 class not found
When the client submits a task to the cluster, an error message is displayed: 【com.hazelcast.nio.serialization.HazelcastSerializatcionException: java.lang.ClassNotFoundException: orgg.apache.seatunnel.connectors.seatunnel.feishu.source.Feishusource】
由于启动的 client 的 SEATUNNEL_HOME 目录是本地的,然后本地启动cluster,提交成功!
Since the SEATUNNEL_HOME directory of the started client is local, and then the cluster is started locally, the submission is successful!
最后发现原因是client提交的任务,SEATUNNEL_HOME 是需要与 cluster 中的保持一致。
Finally, I found that the reason was the task submitted by the client. SEATUNNEL_HOME needs to be consistent with that in the cluster.
除了使用 REST 提交,有没有任何可以解决的办法呢?
Is there any solution besides using REST submission?
SeaTunnel Version
2.3.8
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
Zeta
Java or Scala Version
Java
Screenshots
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: