tango-controls-hdbpp / libhdbpp-timescale Goto Github PK

Many assert calls are done at the beginning of DbConnection::storeParameterEvent method:

The library shall not crash in this use case.
There is nothing to impose our users to put something in every parameter of an attribute configuration and the HdbEventSubscriber should not have this role. We shouldn't make this assumption that every parameter composing an attribute configuration shall not be empty.

The merge/revert of the enum support, which branched from the project-build2 branch has caused problems trying to roll all the project-build2 changes in (many are missing, since they were previously reverted).

This needs fixing and a PR raising for project-build2.

When compiling libhdbpp-timescale on Debian Buster, gcc 8.3 is reporting the following compilation warning:

libhdbpp-timescale/src/AttributeName.cpp:293.1: warning: no return statement in function returning non-void [-Wreturn-type]
}
^

This method should return *this to be able to chain this operator.

Hello.

Current stable version (13) of PostgreSQL is not supported by pre-2 TimescaleDB v1.7.
There were some major changes between Timescale 1.x and 2.x https://docs.timescale.com/timescaledb/latest/overview/release-notes/changes-in-timescaledb-2/

I don't really know what is under the hood of libhdbpp-timescale. Can you please check changelog and clarify if I must stay on PSQL 12 and TDB 1.7 or can use new versions without problems?

Hello.
I've installed timescale-based library and trying to start EventSubscriber.
With -v5 option I have output message:

FATAL sys/tools/hdb++es-srv PushThreadShared: error connecting DB: Configuration parsing error: mandatory configuration parameter: connect_string not found

I've also added desc and origin error output:

Configuration parsing error: mandatory configuration parameter: connect_string not found HdbppTimescaleDb.cpp:getConfigParam:78

There is a LibConfiguration property in ES server

libname=libhdb++timescale.so
host=localhost
port=5432
dbname=hdb
user=hdb_event_sub
password=hdbpp

DB and users was created from .sql files.

Is the way of configuring changed? How can I fix it?

Debian 10, Tango 9.3.4-rc1, everything else is latest version cloned from github.

If log_file_name LibConfiguration property parameter is set to /tmp/hdbpp/my_wonderful_log.log and /tmp/hdbpp directory does not exist yet, it would be convenient to try to create this directory instead of logging an error on the console as it is now.