You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SQL catalog requires a database for its backend. PyIceberg supports PostgreSQL and SQLite through psycopg2. The database connection has to be configured using the `uri` property. The init_catalog_tables is optional and defaults to True. If it is set to False, the catalog tables will not be created when the SQLCatalog is initialized. See SQLAlchemy's [documentation for URL format](https://docs.sqlalchemy.org/en/20/core/engines.html#backend-specific-urls):
Copy file name to clipboardExpand all lines: mkdocs/docs/contributing.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -234,8 +234,6 @@ Deprecated in 0.1.0, will be removed in 0.2.0. The old_property is deprecated. P
234
234
235
235
For the type annotation the types from the `Typing` package are used.
236
236
237
-
PyIceberg offers support from Python 3.9 onwards, we can't use the [type hints from the standard collections](https://peps.python.org/pep-0585/).
238
-
239
237
### Third party libraries
240
238
241
239
PyIceberg naturally integrates into the rich Python ecosystem, however it is important to be hesitant adding third party packages. Adding a lot of packages makes the library heavyweight, and causes incompatibilities with other projects if they use a different version of the library. Also, big libraries such as `s3fs`, `adlfs`, `pyarrow`, `thrift` should be optional to avoid downloading everything, while not being sure if is actually being used.
Copy file name to clipboardExpand all lines: mkdocs/docs/how-to-release.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ This guide outlines the process for releasing PyIceberg in accordance with the [
30
30
## Requirements
31
31
32
32
* A GPG key must be registered and published in the [Apache Iceberg KEYS file](https://downloads.apache.org/iceberg/KEYS). Follow [the instructions for setting up a GPG key and uploading it to the KEYS file](#set-up-gpg-key-and-upload-to-apache-iceberg-keys-file).
33
+
* Permission to update the `KEYS` artifact in the [Apache release distribution](https://dist.apache.org/repos/dist/release/iceberg/) (requires Iceberg PMC privileges).
33
34
* SVN Access
34
35
* Permission to upload artifacts to the [Apache development distribution](https://dist.apache.org/repos/dist/dev/iceberg/) (requires Apache Committer access).
35
36
* Permission to upload artifacts to the [Apache release distribution](https://dist.apache.org/repos/dist/release/iceberg/) (requires Apache PMC access).
@@ -405,5 +406,12 @@ cd icebergsvn
405
406
echo"">> KEYS # append a newline
406
407
gpg --list-sigs <YOUR KEY ID HERE>>> KEYS # append signatures
407
408
gpg --armor --export <YOUR KEY ID HERE>>> KEYS # append public key block
408
-
svn commit -m "add key for <YOUR NAME HERE>"
409
+
svn commit -m "add key for <YOUR NAME HERE>"# this requires Iceberg PMC privileges
409
410
```
411
+
412
+
<!-- prettier-ignore-start -->
413
+
414
+
!!! note
415
+
Updating the `KEYS` artifact in the `release/` distribution requires Iceberg PMC privileges. Please work with a PMC member to update the file.
0 commit comments