[GitHub] [flink] JunRuiLee commented on pull request #23429: test

2023-09-16 Thread via GitHub
JunRuiLee commented on PR #23429: URL: https://github.com/apache/flink/pull/23429#issuecomment-1722367758 @flinkbot run azure -- 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

[GitHub] [flink] JunRuiLee closed pull request #23420: test

2023-09-16 Thread via GitHub
JunRuiLee closed pull request #23420: test URL: https://github.com/apache/flink/pull/23420 -- 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:

[jira] [Updated] (FLINK-30519) Add e2e tests for operator dynamic config

2023-09-16 Thread Flink Jira Bot (Jira)
[ https://issues.apache.org/jira/browse/FLINK-30519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-30519: --- Labels: stale-assigned stale-critical starter (was: stale-assigned starter) I am the

[jira] [Updated] (FLINK-32522) Kafka connector should depend on commons-collections instead of inherit from flink

2023-09-16 Thread Flink Jira Bot (Jira)
[ https://issues.apache.org/jira/browse/FLINK-32522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-32522: --- Labels: auto-deprioritized-major pull-request-available (was: pull-request-available

[jira] [Commented] (FLINK-26088) Add Elasticsearch 8.0 support

2023-09-16 Thread Matheus Felisberto (Jira)
[ https://issues.apache.org/jira/browse/FLINK-26088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766017#comment-17766017 ] Matheus Felisberto commented on FLINK-26088: Hi everyone, I hope you are well.   I just

[GitHub] [flink-connector-elasticsearch] mtfelisb commented on pull request #53: [FLINK-26088][Connectors/ElasticSearch] Add Elasticsearch 8.0 support

2023-09-16 Thread via GitHub
mtfelisb commented on PR #53: URL: https://github.com/apache/flink-connector-elasticsearch/pull/53#issuecomment-1722311553 Guys, I wrote a bunch of tests heavily inspired by https://github.com/apache/flink-connector-opensearch/pull/5 since they have very similar implementations. Thanks

[GitHub] [flink] Jiabao-Sun commented on pull request #23200: [FLINK-32850][flink-runtime][JUnit5 Migration] Module: The io package of flink-runtime

2023-09-16 Thread via GitHub
Jiabao-Sun commented on PR #23200: URL: https://github.com/apache/flink/pull/23200#issuecomment-1722273836 Hi @reswqa, could you help review this PR when you have time? Many thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [flink] flinkbot commented on pull request #23429: test

2023-09-16 Thread via GitHub
flinkbot commented on PR #23429: URL: https://github.com/apache/flink/pull/23429#issuecomment-1722243119 ## CI report: * 6bfa6a72d3191544cb7e94375d935cf0bcc2293d UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run azure`

[GitHub] [flink] JunRuiLee opened a new pull request, #23429: test

2023-09-16 Thread via GitHub
JunRuiLee opened a new pull request, #23429: URL: https://github.com/apache/flink/pull/23429 run ci -- 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:

[GitHub] [flink-connector-aws] Samrat002 closed pull request #97: [POC]Flink Connector Redshift

2023-09-16 Thread via GitHub
Samrat002 closed pull request #97: [POC]Flink Connector Redshift URL: https://github.com/apache/flink-connector-aws/pull/97 -- 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

[GitHub] [flink-connector-aws] Samrat002 opened a new pull request, #97: [POC]Flink Connector Redshift

2023-09-16 Thread via GitHub
Samrat002 opened a new pull request, #97: URL: https://github.com/apache/flink-connector-aws/pull/97 ## Purpose of the change *For example: Implements the Table API for the Kinesis Source.* ## Verifying this change Please make sure both new and modified tests in

[GitHub] [flink] flinkbot commented on pull request #23428: [FLINK-33095] Job jar issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR.

2023-09-16 Thread via GitHub
flinkbot commented on PR #23428: URL: https://github.com/apache/flink/pull/23428#issuecomment-1722170441 ## CI report: * 87add303df04bf86b615e4b01ad865438f91292f UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run azure`

[jira] [Updated] (FLINK-33095) Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR

2023-09-16 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/FLINK-33095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-33095: --- Labels: pull-request-available (was: ) > Job jar related issue should be reported as

[GitHub] [flink] surendralilhore opened a new pull request, #23428: [FLINK-33095] Job jar issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR.

2023-09-16 Thread via GitHub
surendralilhore opened a new pull request, #23428: URL: https://github.com/apache/flink/pull/23428 When submitting a job with incorrect parameters, such as an invalid entry class, the current response is an internal server error. To enhance the user experience and consistency, it is

[jira] [Updated] (FLINK-33095) Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR

2023-09-16 Thread Surendra Singh Lilhore (Jira)
[ https://issues.apache.org/jira/browse/FLINK-33095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surendra Singh Lilhore updated FLINK-33095: --- Attachment: image-2023-09-16-13-21-24-634.png > Job jar related issue

[jira] [Commented] (FLINK-33095) Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR

2023-09-16 Thread Surendra Singh Lilhore (Jira)
[ https://issues.apache.org/jira/browse/FLINK-33095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765922#comment-17765922 ] Surendra Singh Lilhore commented on FLINK-33095: Current response from server :

[jira] [Updated] (FLINK-33095) Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR

2023-09-16 Thread Surendra Singh Lilhore (Jira)
[ https://issues.apache.org/jira/browse/FLINK-33095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surendra Singh Lilhore updated FLINK-33095: --- Attachment: image-2023-09-16-13-20-15-052.png > Job jar related issue

[jira] [Updated] (FLINK-33095) Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR

2023-09-16 Thread Surendra Singh Lilhore (Jira)
[ https://issues.apache.org/jira/browse/FLINK-33095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surendra Singh Lilhore updated FLINK-33095: --- Attachment: (was: image-2023-09-16-13-17-14-869.png) > Job jar related

[jira] [Created] (FLINK-33095) Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR

2023-09-16 Thread Surendra Singh Lilhore (Jira)
Surendra Singh Lilhore created FLINK-33095: -- Summary: Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR Key: FLINK-33095 URL:

[jira] [Updated] (FLINK-33095) Job jar related issue should be reported as BAD_REQUEST instead of INTERNAL_SERVER_ERROR

2023-09-16 Thread Surendra Singh Lilhore (Jira)
[ https://issues.apache.org/jira/browse/FLINK-33095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surendra Singh Lilhore updated FLINK-33095: --- Attachment: (was: image-2023-09-16-13-17-49-945.png) > Job jar related