This is an automated email from the ASF dual-hosted git repository.

zeroshade pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg-go.git


The following commit(s) were added to refs/heads/main by this push:
     new a9bb6fd24 docs: set AWS_S3_ENDPOINT in integration test instructions 
(#2456)
a9bb6fd24 is described below

commit a9bb6fd24444f49de987aa949cd6c26d9691b9df
Author: Ayaan <[email protected]>
AuthorDate: Mon Nov 9 23:08:18 2026 +0530

    docs: set AWS_S3_ENDPOINT in integration test instructions (#2456)
    
    * docs: set AWS_S3_ENDPOINT in integration test instructions
    
    Signed-off-by: Ayaan <[email protected]>
    
    * docs: use localhost S3 endpoint and scope integration test packages
    
    Signed-off-by: Ayaan <[email protected]>
    
    * docs: use absolute README link so it resolves on the docs site
    
    ---------
    
    Signed-off-by: Ayaan <[email protected]>
---
 CONTRIBUTING.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9cab72742..f3bb96150 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -62,9 +62,14 @@ Integration tests require Docker and are gated behind a 
build tag:
 
 ```bash
 docker compose -f internal/recipe/docker-compose.yml up -d rest object-store 
create-bucket --wait
-go test -tags integration ./...
+export AWS_S3_ENDPOINT=http://localhost:9000 AWS_REGION=us-east-1
+go test -tags integration ./catalog/rest/... ./catalog/sql/... 
./table/maintenance/... ./io/gocloud/s3/...
 ```
 
+Without `AWS_S3_ENDPOINT`, the S3-backed tests send requests to real AWS S3 
and fail (for example with a `301 PermanentRedirect`).
+
+This starts only the REST catalog and object store, so it runs only the 
packages they serve. To run the full suite CI runs (Hive, Azure, GCS and 
Spark), see [Integration 
tests](https://github.com/apache/iceberg-go/blob/main/README.md#integration-tests)
 in the README.
+
 #### External REST Catalog Conformance
 
 `TestExternalRestCatalogConformance` runs the catalog conformance suite 
against any REST catalog server. It is skipped unless `REST_CATALOG_URI` is 
set. CI runs it against [Apache Polaris](https://polaris.apache.org/); to do 
the same locally (requires `jq`):

Reply via email to