From 10adb1cb03d4fd2b6ec457b5d8689b24e353bd00 Mon Sep 17 00:00:00 2001 From: Kevin Liu Date: Thu, 29 Feb 2024 20:05:38 -0800 Subject: [PATCH] remove unused references --- mkdocs/docs/configuration.md | 9 --------- pyiceberg/catalog/__init__.py | 1 - 2 files changed, 10 deletions(-) diff --git a/mkdocs/docs/configuration.md b/mkdocs/docs/configuration.md index e1a6d3281b..4a461ccc0d 100644 --- a/mkdocs/docs/configuration.md +++ b/mkdocs/docs/configuration.md @@ -265,15 +265,6 @@ catalog: The In-Memory catalog uses in-memory data-structures to store information. This is useful for test, demo, and playground. Do not use in production as the data is not persisted. -While you can specify In-Memory catalog in the configuration file like this, it is not recommended since information is only persisted for the duration of the function call. - -```yaml -catalog: - default: - type: in_memory - warehouse: /tmp/warehouse # default warehouse location -``` - # Concurrency PyIceberg uses multiple threads to parallelize operations. The number of workers can be configured by supplying a `max-workers` entry in the configuration file, or by setting the `PYICEBERG_MAX_WORKERS` environment variable. The default value depends on the system hardware and Python version. See [the Python documentation](https://docs.python.org/3/library/concurrent.futures.html#threadpoolexecutor) for more details. diff --git a/pyiceberg/catalog/__init__.py b/pyiceberg/catalog/__init__.py index 58a3d5999f..db83658f1f 100644 --- a/pyiceberg/catalog/__init__.py +++ b/pyiceberg/catalog/__init__.py @@ -97,7 +97,6 @@ class CatalogType(Enum): GLUE = "glue" DYNAMODB = "dynamodb" SQL = "sql" - IN_MEMORY = "in_memory" def load_rest(name: str, conf: Properties) -> Catalog: