PyIceberg with Azure Storage Account (500 Internal Server Error)

[C-Zuge]

Question

While using the pyiceberg got some issues/questions that blocked me, mainly regarding an internal server error 500 after the execution of a simple "create_table" function. Since I'm pretty new on iceberg stuff, probably I'm missing something that I don't know more about. Could anyone help me? I created a namespace and list it, but as soon as I try to create a table on my azure storage account I got the same error 500. My credentials are right, but im using the connection string and pointing the "warehouse" parameter to my storage account such as: "abfs://@<storage_account>.dfs.core.windows.net/".

I was looking the dockerfile and didnt saw anything that i should change regarding credentials.

[kevinjqliu]

Pyiceberg can be used as either a client or a server. In the example above, the load_catalog function creates a client using the Pyiceberg library. This client is used to interact with the rest of the ecosystem.

For load_catalog, when given an uri param, the function creates a REST catalog client. Calling the subsequent create_namespace function will send an HTTP request to the REST catalog server address (localhost:8000).

The 500 error is related to a server issue, which means the server running on port 8000 has errored.

Here's the doc on REST catalog configs https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/configuration.md#rest-catalog

[kevinjqliu]

Note you can use the load_catalog function to create other types of catalogs. In the "Getting started" guide, there's an example of creating an on-disk SQLite catalog
https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/index.md#connecting-to-a-catalog

[kevinjqliu]

For the issue with running the REST server with Pyiceberg, I see you've created this issue kevinjqliu/iceberg-rest-catalog#4

I'll answer on that thread

[github-actions]

This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

[github-actions]

This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'