One other note:

I was having trouble building hive getting an error The following artifacts could not be resolved: javax.jms:jms:jar:1.1.

I found that I had to add this to the pom.xml file to get it to resolve. I took this suggestion from https://stackoverflow.com/questions/4908651/the-following-artifacts-could-not-be-resolved-javax-jmsjmsjar1-1.

    <repository>
      <id>repository.jboss.org-public</id>
      <name>JBoss.org Maven repository</name>
      <url>https://repository.jboss.org/nexus/content/groups/public</url>
    </repository>

The artifact is on maven central -> https://search.maven.org/artifact/javax.jms/jms/1.1/jar
I was able to run without error on my machine.

I had to add the hadoop-common dependency to the spark-hive-shims pom directly but otherwise this also built fine on my system. It would be great to get this merged in, I spent much too long fighting w/ the build instructions before looking this issue.

@mitochon I followed steps given at here. I am able to build client aws-glue-datacatalog-hive2-client, and I am not getting 2.3.4-SNAPSHOT as a release version while building hive, instead getting 2.3.4 version in my local m2 directory ~/.m2/repository/org/apache/hive/hive/2.3.4/. But when I run the hive server using the build generated with this patch, I followed steps mentioned at building hive from source to run hive server. I am not able to connect to glue, I have checked that instance has access to connect glue. And when I run the query like show databases and show tables, it is giving default as a only database and empty table lists. Can anyone please help ?

@gaurang101197 you should probably file an issue with more details of your situation

A few sanity checks to try

• Have you updated hive-site.xml and verified the configuration gets picked up?
• You should get a few jars from this build, hive-exec, hive-metastore, and the was-glue client jar.
• Inspect your jar file to see if SessionHiveMetaStoreClientFactory is present in your hive-exec jar

Also as a disclaimer I'm just a contributor, not affiliated with AWS =)

@mitochon I figured out the problem by carefully looking at the patch. In this patch, there is not property called hive.metastore.client.factory.class but instead hive.imetastoreclient.factory.class property is used to provide client class name. I used hive.imetastoreclient.factory.class property in my hive-site.xml instead of hive.metastore.client.factory.class which is provided in README file. Then I got some class not found and method not found exception which I solved by downloading required aws-sdk jar and put them in auxlib folder of hive. And it is working fine now. Thanks. I think we should update property name in README so other don't fall in the same issue.