Is there any official documentation on QuestDB such as setting up a connection when installed on localhost. I realize it’s time series and non-relational. Does it have a web interface or did they leave it out since it is embedded? It is unclear to me what username, password, and drivers to use but I have found that postgress works on other forum topics.
Crickets. Installed ignition-8.3.0-rc1 and testing the Core Historian which looks like Quest DB under the hood. Still not much documentation on purging stale tags or any kind of database management interface.
There isn't. There's a comment on one of the topics about enabling the PostgreSQL-like external port, but everything about this is an internal implementation detail. It is not intended to be managed externally. Ergo, not documented.
1 Like
Thanks for the response. Is there any mechanism to delete stale/obsolete tags? When history gets enabled/disabled on a particular tag will it re-combine with the old history or is it lost? I’m really familiar with the table structure when using sql historian. I’m just trying to relate it to that, like the ‘retired’ field for a particular tag ID. I don’t see how anybody could decide to use this without this basic information.
I don't know all the details, but I think as part of 8.3 in general, I think they were making improvements across all historian providers to handle tag renaming, etc so that history tables aren't required to be manually modified for things like this anymore.
1 Like
I'm not quite sure where this messaging got lost, but the purpose of the new "core" historian is precisely to be a "black box" where you don't have to think about it. It's not "another RDBMS to manage", its "a turn key embedded historian solution", precisely for the people who don't want to think about it.
Among the reasons not to think about it - just because it's questDB today doesn't mean it will be in the future. By choosing to let us control the level of abstraction, you're also choosing to allow us to take over the pain of migrating to some other historian provider if we ever choose to in the future, or make any other optimizations. The second you start intervening in the internal table structure yourself, all bets are off.
2 Likes
Yeah but we had a case where somebody was accidentally storing tags with all null values, for a long time because nobody noticed. It has storage implications. There was also a glitch because they had the settings to store on change, so the historian did not respect the deadband and was storing them as fast as possible, but that’s another subject. I had to delete millions of tags from each monthly file.
QuestDB, the product, does not support deleting values. There is no way to purge stale tags.