Timo Walther created FLINK-22537:
Summary: Add documentation how to interact with DataStream API
Key: FLINK-22537
URL: https://issues.apache.org/jira/browse/FLINK-22537
Project: Flink
Issue T
Thanks Till. Yes you are right. The INFO logging is enabled. It is just
dumped to a file (the FileAppender) other than the console.
There is probably a way to retrieve that log file from AZP. I will ask
other colleagues how to get this later.
On Thu, Apr 29, 2021 at 4:51 PM Till Rohrmann wrote:
ranqiqiang created FLINK-22538:
--
Summary: How to check sql is right before to execute accross API
Key: FLINK-22538
URL: https://issues.apache.org/jira/browse/FLINK-22538
Project: Flink
Issue T
Dian Fu created FLINK-22539:
---
Summary: Restructure the Python dependency management documentation
Key: FLINK-22539
URL: https://issues.apache.org/jira/browse/FLINK-22539
Project: Flink
Issue Type:
Jark Wu created FLINK-22540:
---
Summary: Remove YAML environment file support in SQL Client
Key: FLINK-22540
URL: https://issues.apache.org/jira/browse/FLINK-22540
Project: Flink
Issue Type: Sub-task
Yes, you can click on the test job where a test failed. Then you can click
on 1 artifact produced (or on the overview page on the X published
(artifacts)). This brings you to the published artifacts page where we
upload for every job the logs.
Cheers,
Till
On Fri, Apr 30, 2021 at 9:22 AM Dong Lin
sandy du created FLINK-22541:
Summary: add json format filter params
Key: FLINK-22541
URL: https://issues.apache.org/jira/browse/FLINK-22541
Project: Flink
Issue Type: Improvement
Comp
lqjacklee created FLINK-22542:
-
Summary: npm update automatic
Key: FLINK-22542
URL: https://issues.apache.org/jira/browse/FLINK-22542
Project: Flink
Issue Type: Bug
Components: Runtime
