You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/01/04 08:05:58 UTC

[GitHub] [flink] slinkydeveloper commented on pull request #18215: [FLINK-25392][table-planner]Support new StatementSet syntax in planner and parser

slinkydeveloper commented on pull request #18215:
URL: https://github.com/apache/flink/pull/18215#issuecomment-1004598887


   > do we need transfer all of the tests into assertj when touching a test file?
   
   Yep, it's best effort so you should try to do the best you can, but you're not forced to go too deep ending up changing all the classes of our test infra. Just replacing all the assertions in the file you're touching is fine. Old and new assertions can co-exist.


-- 
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-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org