hanhanzhang commented on PR #7649:
URL: https://github.com/apache/seatunnel/pull/7649#issuecomment-2357259168
> `${FLINK_HOME}/bin/flink run-application
-Dyarn.ship-files='./config/v2.streaming.conf.template'
-Dyarn.classpath.include-user-jar=DISABLED
-Dyarn.provided.usrlib.dir='hdfs://HDFS4001185/user/flink/usrlib/' --target
yarn-application -c org.apache.seatunnel.core.starter.flink.SeaTunnelFlink
/usr/local/service/seatunnel/starter/seatunnel-flink-15-starter.jar --config
v2.streaming.conf.template --name SeaTunnel`
>
> Using the combination of yarn.provided.usrlib.dir along with
yarn.ship-files seems to be a good approach.



Yes, I've thought about it this way. I wouldn't recommend putting SeaTunnel
lib in yarn.provided.lib.dirs. This would require SeaTunnel and Flink
dependency packages to be placed together. I think it might be a good way to
use SeaTunnel Connector as a UDF similar to SQL.
In addition, the yarn.provided.usrlib.dirs means all the jars in the
classpath, the initial plugin design should be to put the plugins needed for
the task in the classpath. What do you think?
--
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]