metadaddy commented on issue #32: URL: https://github.com/apache/polaris/issues/32#issuecomment-2549461304
@lefebsy I'm not sure why it wasn't working before, but my basic sanity check script runs without errors now. Great job! Please do let me know if there's anything I can do to help get this PR merged. ```bash export POLARIS_BEARER_TOKEN="principal:root;realm:default-realm" export S3_LOCATION="s3://metadaddy-polaris/" export AWS_ENDPOINT_URL="https://s3.us-west-004.backblazeb2.com"; export WAREHOUSE="my-b2-warehouse" curl -s -i -X POST -H "Authorization: Bearer ${POLARIS_BEARER_TOKEN}" \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ http://${POLARIS_HOST:-localhost}:8181/api/management/v1/catalogs \ -d "{ \"name\": \"${WAREHOUSE}\", \"id\": 100, \"type\": \"INTERNAL\", \"readOnly\": false, \"properties\": { \"default-base-location\": \"${S3_LOCATION}\" }, \"storageConfigInfo\": { \"storageType\": \"S3_COMPATIBLE\", \"allowedLocations\": [\"${S3_LOCATION}\"], \"s3.endpoint\": \"${AWS_ENDPOINT_URL}\", \"s3.credentials.catalog.access-key-id\": \"AWS_ACCESS_KEY_ID\", \"s3.credentials.catalog.secret-access-key\": \"AWS_SECRET_ACCESS_KEY\", \"s3.credentials.client.access-key-id\": \"AWS_ACCESS_KEY_ID\", \"s3.credentials.client.secret-access-key\": \"AWS_SECRET_ACCESS_KEY\" } }" ``` ```sql SHOW CATALOGS; SHOW SCHEMAS FROM iceberg; SHOW TABLES FROM iceberg.information_schema; DESCRIBE iceberg.information_schema.tables; CREATE SCHEMA IF NOT EXISTS iceberg.my_schema; CREATE TABLE iceberg.my_schema.test_polaris AS SELECT 1 x; SELECT * FROM iceberg.my_schema.test_polaris; INSERT INTO iceberg.my_schema.test_polaris VALUES (2); SELECT * FROM iceberg.my_schema.test_polaris; UPDATE iceberg.my_schema.test_polaris SET x = 3 WHERE x = 2; SELECT * FROM iceberg.my_schema.test_polaris; DELETE FROM iceberg.my_schema.test_polaris WHERE x = 1; SELECT * FROM iceberg.my_schema.test_polaris; ``` -- 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]
