pingtimeout commented on issue #2552:
URL: https://github.com/apache/polaris/issues/2552#issuecomment-3297259842

   I am not able to reproduce this specific issue either.
   
   @dimas-b Note that the current docker compose file does not seem to work 
against `main` because the roleArn property is required, but not provided as 
part of catalog creation.  That's a different issue though.  I slightly updated 
the docker compose file to be able to test in a single command: 
https://github.com/pingtimeout/polaris/tree/minio-issue-2552-docker-compose.  
That branch contains the following changes:
   
   * Add missing roleArn
   * Wait for MinIO bucket to be created before starting Polaris (unnecessary, 
but makes logs easier to read)
   * Add a Spark SQL service in the docker compose for easy testing
   
   First, ensure that the containers are fully deleted:
   
   ```
   $ docker compose -f getting-started/minio/docker-compose.yml down
    ✔ Container minio-spark-sql-1      Removed                                  
                                                                                
                                                                             
0.0s 
    ✔ Container minio-polaris-setup-1  Removed                                  
                                                                                
                                                                             
0.0s 
    ✔ Container minio-polaris-1        Removed                                  
                                                                                
                                                                             
0.0s 
    ✔ Container minio-setup_bucket-1   Removed                                  
                                                                                
                                                                             
0.0s 
    ✔ Container minio-minio-1          Removed                                  
                                                                                
                                                                             
0.0s 
    ✔ Network minio_default            Removed                                  
                                                                                
                                                                             
0.0s
   ```
   
   Second, start everything, verify that the catalog is created:
   
   ```
   $ docker compose -f getting-started/minio/docker-compose.yml up
   [...]
   polaris-setup-1  | Creating a catalog named quickstart_catalog in realm 
POLARIS...
   polaris-setup-1  | { "catalog": { "name": "quickstart_catalog", "type": 
"INTERNAL", "readOnly": false, "properties": { "default-base-location": 
"s3://bucket123" }, "storageConfigInfo": {"storageType":"S3", 
"endpoint":"http://localhost:9000";, "endpointInternal":"http://minio:9000";, 
"pathStyleAccess":true, "roleArn":"arn:aws:iam::123456789012:role/dummy-role"} 
} }
   [...]
   polaris-1        | 2025-09-16 09:48:52,680 INFO  [io.qua.htt.access-log] 
[,POLARIS] [,,,] (executor-thread-1) 10.89.1.4 - root [16/Sep/2025:09:48:52 
+0000] "POST /api/management/v1/catalogs HTTP/1.1" 201 -
   polaris-setup-1  | < HTTP/1.1 201 Created
   [...]
   ```
   
   Third, attach to Spark SQL and run the provided SQL statement:
   
   ```
   $ docker attach $(docker ps -q --filter name=spark-sql)               
   > create table ns.t1 as select 'abc';
   25/09/16 09:44:03 WARN ResolveSessionCatalog: A Hive serde table will be 
created as there is no table provider specified. You can set 
spark.sql.legacy.createHiveTableByDefault to false so that native data source 
table will be created instead.
   25/09/16 09:44:03 WARN ObjectStore: Failed to get database ns, returning 
NoSuchObjectException
   [SCHEMA_NOT_FOUND] The schema `ns` cannot be found. Verify the spelling and 
correctness of the schema and catalog.
   If you did not qualify the name with a catalog, verify the current_schema() 
output, or qualify the name with the correct catalog.
   To tolerate the error on drop use DROP SCHEMA IF EXISTS.
   ```
   
   No permission error.
   
   


-- 
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: issues-unsubscr...@polaris.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to