XiaoHongbo-Hope commented on code in PR #107: URL: https://github.com/apache/paimon-rust/pull/107#discussion_r2890280951
########## dev/docker-compose.yaml: ########## @@ -0,0 +1,41 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. +# +# Spark + Paimon for integration tests: writes tables to a local volume +# so paimon-rust can read them (no MinIO/S3). +# +# Usage: +# 1. Generate test data (run once): +# docker compose -f dev/docker-compose.yaml run --rm spark-paimon +# 2. Run read integration tests on the host: +# PAIMON_TEST_WAREHOUSE=./dev/warehouse cargo test -p paimon-integration-tests read_from_spark +# +# To re-provision: remove dev/warehouse and run step 1 again. + +services: + spark-paimon: + build: + context: ./spark + dockerfile: Dockerfile + volumes: + # Bind warehouse to host so paimon-rust can read it + - /tmp/paimon-warehouse:/tmp/paimon-warehouse + # Run as root to avoid permission issues with mounted volumes + user: root + # Run provision script and exit (data remains in ./warehouse). Review Comment: Does these three path same ussage? -- 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]
