TimeVary 2026 summer - #1690
Open
eshandilcsumb wants to merge 99 commits into
Open
Conversation
…ine function that uses view, also all of Wendy's changes
…nit_v2 function to use said view.
…aily_readings_unit view
…urly_readings_unit view
…er_hourly_readings_unit view
…dings_unit, altered cik table to reflect previous groups work with time varying conversion, added 3rd version of meter line function based on previous groups implementaion of time varying conversions for testing purposes
…ed into meter_hourly_readings_unit view
…_unit implementing CIK table
Currently read-only. Uses fake data, as the Weeks API is not yet implemented.
…_readings_unit so that it no that it no longer has to apply the conversions it self.
… in navbar to "Patterns - Weekly"
* CRUD operations working with back-end * client-side validation * delete confirmation * Spanish and French translations
Omit `id` from the default week values model
docker-compose should not be ignored and should not have to be altered for our time-varying conversion work
…me varying conversions for raw readings.
…nstead of 2.26.1-pg15
…ile as this was create file locks when running tests
… logic to use TimeScaleDB.
…er_line_readings_unit structure and comment. create_hourly_readings and create_prerequisities have been updated to give proper credit to JoBarn for proof-of-concept and foundational research
…removed the TimescaleDB view drop for every restart and TimescaleDB vs materialized view value compare from unit tests
…guideline. Adjusted meter_daily_readings_unit TimeScaleDB view to be the base of group_daily_readings_units
…and removed PostgreSQL materialized views. Resolved migration issue to pg17 and up.
… proper repository in OED, timeVary2026SummerHandover.md
…a better where clause
… reading bulk inserts and removed procedural query codes
…daries and synchronizing aggregate rebuilds.
…for possible code trimming options
Member
|
@eshandilcsumb & @MartinCSUMB Thank you for this contribution. The PR description states the CLA has been signed by all contributors. However, OED records do not have one for @MartinCSUMB . Thus, I would like you to sign the CLA via the link in the description or let me know that you think OED records are off. Once this is done, this PR can be formally reviewed. Please let me know if you have any questions/thoughts. |
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
8 participants
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.
Description
This pull request introduces a TimescaleDB-based reading aggregation implementation for fresh database installations.
The goal of this work is to replace the legacy PostgreSQL materialized-view aggregation approach with a scalable TimescaleDB design that better supports large reading datasets, time-varying unit conversions, and efficient meter and group graph queries.
The new implementation adds:
This change also updates fresh database schema creation to install the TimescaleDB objects in dependency order.
The motivation for this work is to improve aggregation performance and provide a foundation for moving OED reading analytics from legacy materialized views to TimescaleDB. The implementation is integrated for fresh databases, while migration support for existing installations remains future work.
Contributors:
Type of change
Checklist
Limitations