Conversation
212fd35 to
ca0ec94
Compare
plugin/trino-delta-lake/src/main/java/io/trino/plugin/deltalake/DeltaLakeMetadata.java
Outdated
Show resolved
Hide resolved
...o-delta-lake/src/test/java/io/trino/plugin/deltalake/TestDeltaLakeGcsConnectorSmokeTest.java
Outdated
Show resolved
Hide resolved
| } | ||
| } | ||
| catch (FileNotFoundException e) { | ||
| return ImmutableList.of(); |
There was a problem hiding this comment.
why not fail in case that the directory is not present?
There was a problem hiding this comment.
There are tests that rely on this behavior. Directory xyz doesn't exist, and the test checks how many files are in xyz. Seems like a reasonable contract to me
hashhar
left a comment
There was a problem hiding this comment.
Did not look at SmokeTests yet and the changes in DeltaLake plugin.
...rino-delta-lake/src/test/java/io/trino/plugin/deltalake/BaseDeltaLakeConnectorSmokeTest.java
Outdated
Show resolved
Hide resolved
...rino-product-tests/src/main/java/io/trino/tests/product/deltalake/TestDeltaLakeGcsReads.java
Outdated
Show resolved
Hide resolved
testing/trino-product-tests/src/main/java/io/trino/tests/product/TestGroups.java
Outdated
Show resolved
Hide resolved
| prepare_statement: | ||
| - USE ${databases.hive.schema} |
There was a problem hiding this comment.
Question unrelated to this PR - can we use this to for example run CREATE SCHEMA against trino runner?
e.g. File HMS doesn't allow creating views in non-existent schemas so I have some PTs where the test itself runs CREATE SCHEMA IF NOT EXISTS and I'd maybe want the schema creation to happen here.
...main/resources/docker/presto-product-tests/conf/environment/multinode-gcs/iceberg.properties
Show resolved
Hide resolved
.../docker/presto-product-tests/conf/environment/multinode-gcs/hive-site-overrides-template.xml
Show resolved
Hide resolved
.../docker/presto-product-tests/conf/environment/multinode-gcs/core-site-overrides-template.xml
Show resolved
Hide resolved
| private final Path gcpCredentialsFile; | ||
| private final FileSystem fileSystem; | ||
|
|
||
| @Parameters({"gcp-storage-bucket", "gcp-credentials-key"}) |
There was a problem hiding this comment.
How about adding delta. prefix so that we can avoid conflicts in IntelliJ configuration template in other connectors?
There was a problem hiding this comment.
What about testing.? I was hoping to use the same parameters for Hive and Iceberg as well
...o-delta-lake/src/test/java/io/trino/plugin/deltalake/TestDeltaLakeGcsConnectorSmokeTest.java
Outdated
Show resolved
Hide resolved
...o-delta-lake/src/test/java/io/trino/plugin/deltalake/TestDeltaLakeGcsConnectorSmokeTest.java
Outdated
Show resolved
Hide resolved
...duct-tests-launcher/src/main/java/io/trino/tests/product/launcher/suite/suites/SuiteGcs.java
Outdated
Show resolved
Hide resolved
...rino-product-tests/src/main/java/io/trino/tests/product/deltalake/TestDeltaLakeGcsReads.java
Outdated
Show resolved
Hide resolved
|
|
||
| builder.addConnector("hive", forHostPath(dockerFiles.getDockerFilesHostPath("conf/environment/multinode-gcs/hive.properties")), CONTAINER_PRESTO_HIVE_PROPERTIES); | ||
| builder.addConnector("delta", forHostPath(dockerFiles.getDockerFilesHostPath("conf/environment/multinode-gcs/delta.properties")), CONTAINER_PRESTO_ETC + "/catalog/delta.properties"); | ||
| builder.addConnector("iceberg", forHostPath(dockerFiles.getDockerFilesHostPath("conf/environment/multinode-gcs/iceberg.properties")), CONTAINER_PRESTO_ETC + "/catalog/iceberg.properties"); |
There was a problem hiding this comment.
hive & iceberg connectors look unused. Is it for future work?
There was a problem hiding this comment.
Yep, I was going to put tests for Hive and Iceberg up next. I also just thought it'd be handy to have for development on GCS as well, but I can remove them until the next PR if you'd like.
There was a problem hiding this comment.
Got it. There is no need to remove them.
f6ca780 to
58ea1ed
Compare
|
Applied comments above, and included a commit to reduce the test parallelism. I'm hoping that will help the OOM issues on the test branch #12663 (comment) If anyone has better ideas though, let me know |
|
I ran the suite with JMX logging, and looking at the heap usage it increases gradually up to about 3GB and then I guess GC runs and the heap goes back down to about 0.75GB. |
@alexjo2144 please see #12663 (comment) Increasing |
That commit suggests 4g, which sounds like a lot for non-stress tests. |
|
GCS test succeeded in #12663, but it took 59 min (test timeout is 60min). We need to increase the timeout or find a way to shorten the time. |
|
+1 for increasing the the |
fe408fb to
a2e60bf
Compare
|
Updated #12663 |
e280bc2 to
5102b80
Compare
|
Sorry, need one more mirror. Didn't notice the new merge tests during the rebase |
|
One more thing to test. I switched the bucket to a regioned one in us-east so it should be close to the AWS region we run CI in |
11001bb to
9c37bce
Compare
|
@ebyhr can we do another test with secrets when you get a chance? |
509a9a1 to
9c37bce
Compare
...o-delta-lake/src/test/java/io/trino/plugin/deltalake/TestDeltaLakeGcsConnectorSmokeTest.java
Show resolved
Hide resolved
...ing/trino-product-tests/src/main/java/io/trino/tests/product/deltalake/TestDeltaLakeGcs.java
Outdated
Show resolved
Hide resolved
9c37bce to
85de93c
Compare
|
All set, thanks @ebyhr |
.github/workflows/ci.yml
Outdated
There was a problem hiding this comment.
GCS suite looks not running. Probably, this should be steps.check-gcp-secrets.outputs.have_gcp_secrets.
Includes catalogs for the hive, delta lake, and iceberg connectors.
85de93c to
ef59122
Compare
|
Merged, thanks! |
|
🎉 |

Description
Integration and Product tests for running Delta Lake on Google Cloud Storage.
Test only
Delta Lake connector
Not important
Related issues, pull requests, and links
GCS was enabled in #12144
Documentation
(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(x) No release notes entries required.
( ) Release notes entries required with the following suggested text: