Reduce cyclomatic complexity of TimescaleDB export module#3463
Open
zfh468 wants to merge 11 commits into
Open
Conversation
…5 in overriding 'Export.export' method
nicolargo
requested changes
Mar 1, 2026
Author
|
All original comments, documentation links, and TODOs have been restored. Code complexity and security issues are also addressed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reduces the cyclomatic complexity of the TimescaleDB export module (glances/exports/glances_timescaledb/init.py) by simplifying control flow and extracting clearer logic boundaries.
Relates to #3460
Problem
The update() method contained duplicated logic for dict-based and list-based plugin stats handling, nested conditional branches, and inline preprocessing steps mixed with SQL preparation logic.
This resulted in increased cyclomatic complexity and reduced readability, making future maintenance more difficult.
Solution
Refactored the module to:
The refactor preserves the existing SQL generation logic, table schema structure, segmentation behavior, and normalization rules.
Changes
glances/exports/glances_timescaledb/init.py:
Testing
Note: Full pytest suite was partially limited locally due to environmental dependencies, but module integrity was verified via manual import.
Checklist