Yes, it works. Just make sure you turn off ignition’s features for managing the history tables. This includes data partitioning, pruning, and pre-processing. You are are left with the single history table remaining. At this point, you need knowledge of timescale functionality and how to make that history table into a hypertable. It gets slightly complicated if you are not very comfortable with postgres or SQL.
Things you will need to setup on the table (some optional):
- create hyper table and define how big each “chunk” will be in terms of time. This is timescale’s terminology for data partitions.
- Create function that translates the timestamp column for timescale standard
- define a “now” function for getting current time in the same format
- setup table for compression
- add a policy for compressing chunks
- add a policy for dropping “chunks”. This is timescale’s data pruning.
Their website has some good documentation for performing these operations.