Skip to main content

JDBC Catalog

ParameterSample ValueDescription
JDBC URLjdbc:postgresql://host.docker.internal:5432/icebergJDBC URL for connecting to the PostgreSQL catalog.
JDBC UsernameicebergUsername for the PostgreSQL catalog.
JDBC PasswordpasswordPassword for the PostgreSQL catalog.
Iceberg S3 Paths3a://warehouseS3 path where the Iceberg data/metadata files will be stored.
S3 Endpointhttp://host.docker.internal:9000Endpoint for the S3 service (Minio in this case).
Use SSL for S3falseBoolean flag to determine if SSL should be used when connecting to S3.
Use Path Style for S3trueUse path-style addressing for the S3 API.
AWS Access KeyadminAWS access key (or Minio key for local testing).
AWS Regionus-east-1Specifies the AWS region associated with the S3 bucket where the data is stored.
AWS Secret KeypasswordAWS secret key (or Minio secret for local testing).
Iceberg Databaseolake_icebergName of the database to be created in the Iceberg catalog.

You can query the data via:

SELECT * FROM CATALOG_NAME.ICEBERG_DATABASE_NAME.TABLE_NAME;
  • CATALOG_NAME can be: jdbc_catalog, hive_catalog, rest_catalog, etc.
  • ICEBERG_DATABASE_NAME is the name of the Iceberg database you created / added as a value in destination.json file.

If you are build olake locally (using ./build.sh command), change the config to:

  1. jdbc_url": "jdbc:postgresql://localhost:5432/iceberg"
  2. s3_endpoint": "http://localhost:9000"

For S3 related permissions which is needed to write data to S3, refer to the AWS S3 Permissions documentation.

info

If you wish to test out the REST Catalog locally, you can use the docker-compose setup. The local test setup uses Minio as an S3-compatible storage and other all supported catalog types.

You can then setup local spark to run queries on the iceberg tables created in the local test setup.


Need Assistance?

If you have any questions or uncertainties about setting up OLake, contributing to the project, or troubleshooting any issues, we’re here to help. You can:

  • Email Support: Reach out to our team at hello@olake.io for prompt assistance.
  • Join our Slack Community: where we discuss future roadmaps, discuss bugs, help folks to debug issues they are facing and more.
  • Schedule a Call: If you prefer a one-on-one conversation, schedule a call with our CTO and team.

Your success with OLake is our priority. Don’t hesitate to contact us if you need any help or further clarification!