Have you tried setting "hive.in.test" to "true"? This should get rid of
many of the "table X does not exist" errors you were seeing. I know of two
other projects that have upgraded from Hive 2 to 3 that run embedded
Metastore Services and/or HS2 instances, the pull requests from these might
give yo
So, last update on my issues. I have reached a point where the embedded
hive server starts up without any exceptions thrown. It seems that I needed
to disable direct sql. It's not entirely clear to me what that setting
actually does, but it seems to clear up the SQL execution warnings in
embedded m
Correction, there are still exceptions related to the metastore not having
schemas created, but they are not keeping the service from starting. Things
still seem a little sketchy - this is a lot of exceptions for each start up
which makes me worried. I'd love to hear if anyone had any other ideas
a
Hi Stamatis,
Thanks for the input, I just tried using a memory database within derby but
it seems like it didn't address the core problem - Still getting errors
that the self test query is failing because the tables within the metastore
do not exist.
I took a look around your project, and clearly
Hi James,
I am doing something similar with the difference that everything runs on
docker [1].
I am using Hive 3.1 (HDP though) but things work fine at least with
in-memory derby.
javax.jdo.option.ConnectionURL
jdbc:derby:memory:metastore;create=true
Best,
Stamatis
[1]
Hey folks,
I have a project where I test with Hive using an embedded HiveServer2
instance within a JVM running integration tests. This has worked for Hive
1.2.2 in the past, and I've been able to get it to work with Hive 2.3.8,
but have been having trouble getting it working on Hive 3.0+
The erro
