-
Notifications
You must be signed in to change notification settings - Fork 381
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
[#4633] refactor(integration-test): move the tests in integration-test module into their corresponding modules #4628
Conversation
fe1ac6d
to
5635159
Compare
@diqiu50 could you plz help to review the Trino part? |
5635159
to
6a96485
Compare
trino-connector/integrate-test/build/*.log | ||
trino-connector/integrate-test/build/*.tar | ||
distribution/package/logs/gravitino-server.out | ||
distribution/package/logs/gravitino-server.log |
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.
Is Missing the docker container's logs?
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.
fixed
6a96485
to
019dc8f
Compare
The test of the client will depend on server. I don't think it's correct behaviour. An integration test depends on multiple catalogs. We shouldn't remove integration-test module. |
Each catalog has its own integration test. If the server changes, we can use client integration tests to verify it. Therefore, I removed the integration-test module. |
If we need a federated catalog test, we should put it into which catalog? |
It depends on your test purpose, the test can be added to the integration-test of |
c5eeb9d
to
6b17a13
Compare
I was thinking that there may be some APIs that only exist on the server side, and don't have client APIs, where do we put that tests? |
I think the situation you mentioned can be covered by server's UT, and if necessary, |
close and reopen for rerun CI |
a68e2ca
to
becb0d9
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.
Shall we put these under resource folder?
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.
I just kept it in its original position. Let me give it a try.
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.
After trying this, I would suggest to leave it as it currently is, so that other modules can access it via a fixed path. If it is placed in a resource file, it needs to be accessed via the class path, which adds complexity when calling across modules.
a96fe1c
to
dbf4bf3
Compare
- clients/filesystem-hadoop3/** | ||
- clients/filesystem-hadoop3-runtime/** |
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.
The change of gvfs should not trigger the Trino tests.
- server/** | ||
- server-common/** | ||
- trino-connector/** | ||
- docs/open-api/** |
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.
Also here. Can you please carefully check this to make sure only the related changes will trigger the tests.
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.
I plan to fix them all in #4827, do you suggest doing it in this PR?
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.
I'm fine doing it in #4827 .
@@ -16,7 +16,7 @@ | |||
* specific language governing permissions and limitations | |||
* under the License. | |||
*/ | |||
package org.apache.gravitino.integration.test.store.relational.service; | |||
package org.apache.gravitino.storage.relational.service; |
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.
What is the purpose of changing this package name?
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.
Because this class is actually a UT, not IT, it tests the interface of FilesetMetaService
. So I changed the package name
@@ -0,0 +1,73 @@ | |||
/* |
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.
For the web module, should you also do like trino module, to have two submodules under the web module?
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.
What's your opinion on this?
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.
yeah, it's better to follow the same specifications. I refactored the web module to the same
ac4ae9b
to
1d5c20b
Compare
@@ -627,7 +625,7 @@ tasks { | |||
} | |||
|
|||
val compileTrinoConnector by registering { | |||
dependsOn("trino-connector:copyLibs") | |||
dependsOn("trino-connector:trino-connector:copyLibs") |
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.
Can you please check if the LICENSE, NOTICE, and DISCLAIMER are correctly copied to the release package for trino-connector, web, and gravitino packages? Since the trino and web package location has been changed, I guess it will be failed to locate the file, can you please check and fix?
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.
Also check the compileDistribution
and assembleDistribution
, to see if they still work or not?
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.
I have checked them all, they work well
1d5c20b
to
0888a0d
Compare
There're some test errors, can you please fix them? |
1600c3b
to
c9b9ffc
Compare
What changes were proposed in this pull request?
Why are the changes needed?
Fix: #4633
Does this PR introduce any user-facing change?
no
How was this patch tested?
CI passed