hi most of metadata tables have a bit flags field that is used when metadata upgrade is not possible. We can check to see if all metadata tables have that field and if not, add it. Also, if some of the existing flag fields are being used, can check to see if it makes sense to add a separate field to that table instead of using a flag bit. anoop
-----Original Message----- From: Dave Birdsall [mailto:[email protected]] Sent: Thursday, June 2, 2016 11:45 AM To: [email protected] Subject: RE: Metadata changes for Trafodion 2.1? Hi, Thanks, Anu. Does anyone else have a metadata change planned for Trafodion 2.1? Dave -----Original Message----- From: Anuradha Hegde [mailto:[email protected]] Sent: Wednesday, June 1, 2016 2:23 PM To: [email protected] Subject: RE: Metadata changes for Trafodion 2.1? Yes, I want to add additional columns to repository tables and plan to do that for R2.1 Thanks Anu -----Original Message----- From: Dave Birdsall [mailto:[email protected]] Sent: Wednesday, June 1, 2016 2:20 PM To: [email protected] Subject: Metadata changes for Trafodion 2.1? Hi, I would like to add an index to the TABLE_CONSTRAINTS metadata table in release Trafodion 2.1, to improve DDL concurrency. Metadata changes imply changes to upgrade, along with install testing, and just making sure development instances behave reasonably when the new code changes appear. So it is probably good to batch metadata changes together to reduce the amount of work. So, I wanted to ask: Is anyone else planning a metadata change in release Trafodion 2.1? Thanks, Dave
