Myasuka commented on pull request #19029: URL: https://github.com/apache/flink/pull/19029#issuecomment-1069090826
I compared the `flink-table` module logs in the [CI of this PR](https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=32777&view=artifacts&pathAsName=false&type=publishedArtifacts) with another [CI](https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=33106&view=artifacts&pathAsName=false&type=publishedArtifacts). In the CI running, I can see tests which just use local working directory for RocksDB state backend: ~~~ java Finished building RocksDB keyed state-backend at tmp_575da98d-5390-44fb-9e4c-2beaa05bb47c/job_ea6f78e05c817e20cdc6d80df39f7538_op_KeyedProcessOperator_7a62a488b6629c3cc1699b7c08f3c593__1_1__uuid_e9155b5d-a3cd-469e-b1f8-a080c9bda7aa. ~~~ On the other hand, with this PR, all RocksDB state backend would use folders under `/tmp`: ~~~java Finished building RocksDB keyed state-backend at /tmp/tmp_8e74677c-a194-41df-9ce0-9209273c93de/job_955973f2518d3427585bedbd97fbb3ff_op_KeyedProcessOperator_7d3304e531c6834bde12a02fb1e9ad7f__1_1__uuid_5456c3c8-f69c-479a-9423-7583d474c6ea. ~~~ Maybe a junit temp dir is better, and I don't have strong objection for current solution. -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
