Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warehouse path is always required for Glue catalog, even when there isn't one #941

Open
omerhadari opened this issue Feb 3, 2025 · 0 comments

Comments

@omerhadari
Copy link
Contributor

The warehouse config prop for Glue catalog is required, but it isn't always known or required. The Glue catalog ID is enough in order to resolve metadata locations.

Moreover - I don't think this path is used for anything but protocol (FileIO type) inference? I was able to work around this issue by passing the correct Glue catalog ID (which is the AWS account ID) and s3:// as the warehouse, with no issue.

In my opinion warehouse should be replaced with something like FileIO type and only the Glue catalog ID should be required, but for backwards compatibility not passing warehouse should at least be allowed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant