Curious. Will the meta-data versions for EsgynDB and TrafodionDB will evolve on their own?
On Wed, Jun 15, 2016 at 11:37 AM, Anoop Sharma <[email protected]> wrote: > yes, that comment refers to the older metadata version. > > We can remove that comment and refer to the version > enum in CmpSeabaseDDLincludes.h. That enum will > always contain correct old/new metadata versions. > > This is the content of that file (comment is correct there): > > // new metadata version 1.1.0 changed for release 1.1.0. > // Old metadata version 3.0. > enum { > METADATA_MAJOR_VERSION = 1, > METADATA_OLD_MAJOR_VERSION = 3, > METADATA_MINOR_VERSION = 1, > METADATA_UPDATE_VERSION = 0, > METADATA_OLD_MINOR_VERSION = 0, > METADATA_OLD_UPDATE_VERSION = 0, > DATAFORMAT_MAJOR_VERSION = 1, > DATAFORMAT_MINOR_VERSION = 1 > }; > anoop > > -----Original Message----- > From: Dave Birdsall [mailto:[email protected]] > Sent: Wednesday, June 15, 2016 9:31 AM > To: [email protected] > Subject: RE: Trafodion 2.1 metadata changes > > Hi Anoop, > > Thanks. I saw 2.3 here: > > > /////////////////////////////////////////////////////////////////////////////// > // *** Current Definition *** > // > // Current metadata tables definition for Metadata Version 2.3 // (Major > version = 2, Minor version = 3) > > /////////////////////////////////////////////////////////////////////////////// > > This is in the current version of sqlcomp/CmpSeabaseDDLmd.h. > > I'm guessing this is simply a matter of the comments being out-of-date? > > Dave > > -----Original Message----- > From: Anoop Sharma [mailto:[email protected]] > Sent: Wednesday, June 15, 2016 9:27 AM > To: [email protected] > Subject: RE: Trafodion 2.1 metadata changes > > Dave, on version numbering. > Where do you see major version of 2 and minor version of 3? > Current metadata major/minor version is 1/1 as defined in the following > enum. > It might be good to match metadata version number to the release number. So > changed metadata major/minor version will be 2/1. That will tell which > release metadata version changed. > > enum { > METADATA_MAJOR_VERSION = 1, > METADATA_OLD_MAJOR_VERSION = 3, > METADATA_MINOR_VERSION = 1, > METADATA_UPDATE_VERSION = 0, > METADATA_OLD_MINOR_VERSION = 0, > METADATA_OLD_UPDATE_VERSION = 0, > DATAFORMAT_MAJOR_VERSION = 1, > DATAFORMAT_MINOR_VERSION = 1 > }; > > > Apache Trafodion Conversational Interface 2.1.0 Copyright (c) 2015-2016 > Apache Software Foundation > >>get version of metadata; > > Current Version 1.1.0. Expected Version 1.1.0. > Metadata is current. > > --- SQL operation complete. > > -----Original Message----- > From: Dave Birdsall [mailto:[email protected]] > Sent: Wednesday, June 15, 2016 9:22 AM > To: [email protected] > Subject: RE: Trafodion 2.1 metadata changes > > Thanks, Roberta. Will look into it. > > Just curious: What happens in release 2.0 if library management has not > been > added? And is it possible to "un-add" it? > > -----Original Message----- > From: Roberta Marton [mailto:[email protected]] > Sent: Wednesday, June 15, 2016 9:19 AM > To: [email protected] > Subject: RE: Trafodion 2.1 metadata changes > > In release 2.0 we added library management and we did not support an > upgrade > operation. > So, you may want to check to see if library management has been added, if > not add it. > The command to add library management is "initialize trafodion, create > library management" > > Roberta > > -----Original Message----- > From: Dave Birdsall [mailto:[email protected]] > Sent: Wednesday, June 15, 2016 9:09 AM > To: [email protected] > Subject: Trafodion 2.1 metadata changes > > Hi Trafodion developers, > > > > So far I know of the following metadata changes for Trafodion 2.1. > > > > 1. I want to add an index to TABLE_CONSTRAINTS to improve DDL > concurrency (JIRA TRAFODION-2037) > > 2. Anu wishes to add a couple of columns to one of the Repository > tables > > > > I’m guessing I should just increase the metadata minor version (from 3 to > 4) and leave the major version (2) as-is. Does that sound right to you? > > > > Dave > -- Regards, --Qifan
