Hi Chaoran, You will have to use the scripts from "standalone-metastore/src/main/sql/" directory instead of the ones from the old "metastore/scripts/upgrade" directory. The issue is that the package.jdo reflects the new changes in the schema where as the old schema files do not have these changes.
The simplest way I found was to, after running a full build, "cp standalone-metastore/src/main/sql/derby/*.sql packaging/target/apache-*/apache*/scripts/metastore/derby/" and then use schematool to install the schema. Hope this helps. Thanks Naveen On Wed, Mar 28, 2018 at 10:11 AM, Chaoran Yu <[email protected]> wrote: > Did you mean running "./bin/schematool -dbType derby -initSchema”? > > That didn’t help. > > > On Mar 28, 2018, at 02:09, Mahesh Kumar Behera <[email protected]> > wrote: > > Try rebuilding your metastore db using the schema tool .. > > *From: *Chaoran Yu <[email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Wednesday, March 28, 2018 at 10:53 AM > *To: *"[email protected]" <[email protected]> > *Subject: *Hive master branch broken? > > Hi, > > I made some changes to a local Hive repo based on the latest master > branch. But somehow I got the following error when running a "CREATE TABLE" > statement in Hive shell: > > org.apache.hadoop.hive.ql.metadata.HiveException: > MetaException(message:Insert of object "org.apache.hadoop.hive. > metastore.model.MSerDeInfo@ace2408" using statement "INSERT INTO SERDES > (SERDE_ID,DESCRIPTION,DESERIALIZER_CLASS,"NAME", > SERDE_TYPE,SLIB,SERIALIZER_CLASS) VALUES (?,?,?,?,?,?,?)" failed : > 'DESCRIPTION' is not a column in table or VTI 'APP.SERDES'.) > FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask. > MetaException(message:Insert of object "org.apache.hadoop.hive. > metastore.model.MSerDeInfo@ace2408" using statement "INSERT INTO SERDES > (SERDE_ID,DESCRIPTION,DESERIALIZER_CLASS,"NAME", > SERDE_TYPE,SLIB,SERIALIZER_CLASS) VALUES (?,?,?,?,?,?,?)" failed : > 'DESCRIPTION' is not a column in table or VTI 'APP.SERDES'.) > > No matter what table name or schema I create, I got the same error. I > remember testing my changes about three weeks ago using the master branch > back then, everything was working. It only started failing today after I > merged the latest commits in master. > > Is anyone aware of recent commits that might break this write code path? > And do we know when the next release of Hive is coming out? > > Thank you, > Chaoran Yu > > >
