From 306f4de10d0b8152c2b07b77f2b582a287fa07e9 Mon Sep 17 00:00:00 2001 From: "Mahadik, Mukul Chandrakant" Date: Thu, 1 Aug 2024 01:09:08 -0700 Subject: [PATCH] Removed continue_on_error parameter to load timeseries function This was causing the exception handling to kick in with the flag considered and no data was being inserted in the database --- emission/purge_restore/restore_data.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/emission/purge_restore/restore_data.py b/emission/purge_restore/restore_data.py index 723dca35b..94b34d1ac 100644 --- a/emission/purge_restore/restore_data.py +++ b/emission/purge_restore/restore_data.py @@ -35,4 +35,5 @@ def run_restore_data_pipeline(self, user_id, file_name): time_query = espq.get_time_range_for_restore_data(user_id) entries = json.load(gzip.open(file_name + ".gz"), object_hook = esj.wrapped_object_hook) self._last_processed_ts = entries[-1]['metadata']['write_ts'] - lmtfr.load_multi_timeline_for_range(file_name, continue_on_error=True) + # lmtfr.load_multi_timeline_for_range(file_name, continue_on_error=True) + lmtfr.load_multi_timeline_for_range(file_name)