[
https://issues.apache.org/jira/browse/FLINK-26102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491814#comment-17491814
]
Dian Fu edited comment on FLINK-26102 at 2/14/22, 6:34 AM:
-----------------------------------------------------------
Hi [~waittting], you should post this kind of question in the [user mailing
list|https://flink.apache.org/gettinghelp.html#user-mailing-list] instead of
JIRA. Besides, I suggest you post more information about the question to help
others identify the problem, e.g. the exception stack, the sample code, etc.
was (Author: dianfu):
Hi [~waittting], you should post this kind of question in go to the [user
mailing list|https://flink.apache.org/gettinghelp.html#user-mailing-list]
instead of JIRA. Besides, I suggest you post more information about the
question to help others identify the problem, e.g. the exception stack, the
sample code, etc.
> connector test by using 'flink run --python'
> ---------------------------------------------
>
> Key: FLINK-26102
> URL: https://issues.apache.org/jira/browse/FLINK-26102
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.13.3
> Reporter: waittting
> Priority: Major
>
> When I used 'flink run --python' to test my connector, I got an error '{*}No
> operations allowed after connection closed.{*}' My connector's code does use
> jdbc conn, but when I use sql-client to test the connector with the same SQL,
> it's ok. So I wonder if there is a problem with the execution environment of
> 'flink run -python'
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
