wombatu-kun commented on code in PR #19217:
URL: https://github.com/apache/hudi/pull/19217#discussion_r3704213484


##########
.github/workflows/hudi_trino_e2e.yml:
##########
@@ -0,0 +1,157 @@
+name: Hudi Trino E2E
+
+on:
+  push:
+    branches:
+      - master
+      - 'release-*'
+      # TEMPORARY: validate the workflow on the dev branch; drop this line
+      # (and the commit that added it) before merging upstream.
+      - trino-e2e-testcontainers
+    paths:
+      - 'hudi-trino/**'
+      - 'docker/trino/**'
+      - 'docker/compose/docker-compose_hadoop340_hive2310_spark402*'
+      - 'docker/demo/sparksql-stock-ticks-trino.commands'
+      - 'hudi-integ-test/src/test/java/org/apache/hudi/integ2/**'
+      - '.github/workflows/hudi_trino_e2e.yml'
+  pull_request:
+    branches:
+      - master
+      - 'release-*'
+    paths:
+      - 'hudi-trino/**'
+      - 'docker/trino/**'
+      - 'docker/compose/docker-compose_hadoop340_hive2310_spark402*'
+      - 'docker/demo/sparksql-stock-ticks-trino.commands'
+      - 'hudi-integ-test/src/test/java/org/apache/hudi/integ2/**'
+      - '.github/workflows/hudi_trino_e2e.yml'
+  workflow_dispatch:
+
+concurrency:
+  group: hudi-trino-e2e-${{ github.ref }}
+  cancel-in-progress: ${{ !contains(github.ref, 'master') && 
!contains(github.ref, 'release-') }}
+
+env:
+  MVN_ARGS: -e -ntp -B -V -Dgpg.skip -Djacoco.skip -Pwarn-log

Review Comment:
   `bot.yml` carries `aether.connector.http.retryHandler.*` plus 
`connectionMaxTtl`, with a comment right above it saying Maven 3.9's native 
resolver transport ignores the `maven.wagon.*` names - so both flags added here 
are inert and the `serviceUnavailable=429,500,502,503,504` retry is still 
missing. Please swap in bot.yml's five `aether.connector.http.*` flags verbatim.
   



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to