Actually you are right, it uses my hive metastore running on top of PostgreSQL, and I can see all objects created in Hive before. But I saw in log-file mention about derby, if I rename derby jar-file, my sts installation can not start. And additionally to that, I am able to connect to the STS only via beeline installed locally on the same host with STS. All remote connections via DBeaver which is a JDBC-client are refused. At the same time I am able to connect to Hive with DBeaver. So, I strongly believe that internally it still uses derby.