-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Migrate some of PT environment to Multinode #15960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
451e156 to
ed298a9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please take a look at product tests README.md if there are no references to this env.
|
Thanks! |
ed298a9 to
08ef85a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you remove "singlenode" from trino-product-tests/README.md?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing this. Have updated the README.md
We should use a multinode environment to mimic production like use case.
08ef85a to
5f6d26e
Compare
5f6d26e to
995e15b
Compare
...no-product-tests/src/main/java/io/trino/tests/product/mysql/TestJdbcDynamicFilteringJmx.java
Show resolved
Hide resolved
|
|
|
Shouldn't we use |
|
for local dev purposes it's just wasteful and makes putting breakpoint harder |
Description
Usage of
Standardenvironment is deprecated as it doesn't mimic the production usage, still some of our PT environment use them. This PR migrates a few easy environment. We would migrate them in a phased manner.Release notes
(x) This is not user-visible or docs only and no release notes are required.