haneeshpld commented on issue #5700:
URL: https://github.com/apache/seatunnel/issues/5700#issuecomment-1903348421
@EricJoy2048
I'm not sure if the is issue is occurring here. In my case, I have a working
scenario as well as a non-working scenario.
When containerizing the application (both web and engine), it works if I run
the image on the same machine where it is built. However, when I use the image
on a different machine with almost identical configurations (same OS), it shows
the above error.
Upon checking both the working and non-working scenarios, the above code
produces the same output. Therefore, I im not sure the issue is arising from
this code.
working scenario
Jdbc {
"auto_commit"="true"
"batch_size"=1000
"connection_check_timeout_sec"=30
database=seasink
driver="com.mysql.cj.jdbc.Driver"
"generate_sink_sql"=true
"is_exactly_once"="false"
"max_commit_attempts"=3
"max_retries"="10"
password=xxx
"source_table_name"=Table12348683256512
"support_upsert_by_query_primary_key_exist"="false"
table=pet
"transaction_timeout_sec"=-1
url=“xxxxx”
user=xxx
}
non workig scenario
Jdbc {
"connection_check_timeout_sec"=30
"batch_size"=1000
"is_exactly_once"="false"
"max_commit_attempts"=3
"transaction_timeout_sec"=-1
"max_retries"="10"
"auto_commit"="true"
"support_upsert_by_query_primary_key_exist"="false"
"source_table_name"=Table12340885224320
"generate_sink_sql"=true
database=seasink
table=pet
password=xxxx
driver="com.mysql.cj.jdbc.Driver"
user=xxx
url=“xxxx”
}
there is a file being written after the transformation in st-web
(bin\profile\12261501203968.conf) which is in identical format in both working
and non working scenario, when it is transformed again in the engine side we
get the issue.
--
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]
