Thanks Park for sharing the tests that you did. I will try out for the specific version for my use cases.
Is there any better way/approach where we can have a single meta store and can launch multiple hive clusters of different versions point to the same metastore db. Thanks. On Mon, Dec 9, 2019 at 12:46 PM Sungwoo Park <glap...@gmail.com> wrote: > Not a definitive answer, but my test result might help. I tested with > HiveServer2 1.2.2 and Metastore 2.3.6. Queries in the TPC-DS benchmark > (which only read data and never update) run okay. Creating new tables and > loading data to tables also work okay. So, I guess for basic uses of Hive, > running HiveServer2 1.2 against Metastore 2.3 should be fine. > > What I am not sure about is whether queries involving transactions work > okay when HiveServer2 1.2 connects to Metastore 2.3. Please note that I > have not tested with Hive 1.1. Perhaps those familiar with internals of > Metastore in this mailing list could give more accurate answers. > > As a side note, HiveServer2 2.3 can connect to Metastore 3.1. However, > HiveServer2 1.2 seems to have a problem with connecting to Metastore 3.1. > > Cheers, > > --- gla > > On Mon, Dec 9, 2019 at 2:38 PM Priyam Gupta <pri...@zapr.in> wrote: > >> >> >> Hi, >> >> In order to have single hive metastore supporting different clusters of >> hive, I have upgraded my hive metastore schema (on postgres) from version >> 1.1.0 to version 2.3.0. Will hive cluster on version 1.1.0 work if I point >> it to upgraded metastore db which is as per hive version 2.3.0. >> >> >> Thanks, >> Priyam >> >
