From 68181ad0d6d38b34ed36950181bb2d0fcb1154e3 Mon Sep 17 00:00:00 2001 From: timgl Date: Thu, 28 Mar 2024 12:04:00 +0100 Subject: [PATCH] fix: Fix single property materialization command (#20798) * fix: Fix single property materialization command * default to 0 --- ee/management/commands/materialize_columns.py | 1 - ee/settings.py | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/ee/management/commands/materialize_columns.py b/ee/management/commands/materialize_columns.py index 953110032b31a..f221147e81740 100644 --- a/ee/management/commands/materialize_columns.py +++ b/ee/management/commands/materialize_columns.py @@ -75,7 +75,6 @@ def handle(self, *args, **options): options["property_table"], options["table_column"], options["property"], - 0, ) ], backfill_period_days=options["backfill_period"], diff --git a/ee/settings.py b/ee/settings.py index 903ddf6c3c7ad..448c9ef67aa22 100644 --- a/ee/settings.py +++ b/ee/settings.py @@ -59,7 +59,7 @@ "MATERIALIZE_COLUMNS_ANALYSIS_PERIOD_HOURS", 7 * 24, type_cast=int ) # How big of a timeframe to backfill when materializing event properties. 0 for no backfilling -MATERIALIZE_COLUMNS_BACKFILL_PERIOD_DAYS = get_from_env("MATERIALIZE_COLUMNS_BACKFILL_PERIOD_DAYS", 90, type_cast=int) +MATERIALIZE_COLUMNS_BACKFILL_PERIOD_DAYS = get_from_env("MATERIALIZE_COLUMNS_BACKFILL_PERIOD_DAYS", 0, type_cast=int) # Maximum number of columns to materialize at once. Avoids running into resource bottlenecks (storage + ingest + backfilling). MATERIALIZE_COLUMNS_MAX_AT_ONCE = get_from_env("MATERIALIZE_COLUMNS_MAX_AT_ONCE", 100, type_cast=int)