[ https://issues.apache.org/jira/browse/HIVE-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516856#comment-17516856 ]
Alessandro Solimando commented on HIVE-26112: --------------------------------------------- Sorry I forgot to strip the "derby" part, I meant to keep only the db-agnostic part of the filename (I have edited it). [~pvary]: so you mean that in hive 3.2.0 it is fine to have metastore/scripts/upgrade/hive/hive-schema-3.1.0.hive.sql and no metastore/scripts/upgrade/hive/hive-schema-3.2.0.hive.sql? If the versions don't match between metastore (the sysdb one) and HMS, how can we easily keep the two in sync and make sure nothing slips through the cracks? Maybe we won't fix this for 3.2.0, but I propose to keep them in sync as you have done for _4.0.0-alpha-1_ and _4.0.0-alpha-2_, it will be easier to clarify expectations in this way. I have tried in a local hive-dev-box to manually create "PART_COL_STATS" as an external table against the HMS (postgres in my case), using the same DDL as in the file but adding the missing _BIT_VECTOR_ column, of type _binary_. I can see values in HMS by querying postgres for that column, although I always get NULL via Hive. Is this expected? I am asking because I noticed that among the missing columns, quite a few are of type binary, maybe that's intended? > Missing scripts for metastore > ----------------------------- > > Key: HIVE-26112 > URL: https://issues.apache.org/jira/browse/HIVE-26112 > Project: Hive > Issue Type: Bug > Components: Metastore > Affects Versions: 4.0.0-alpha-2 > Reporter: Alessandro Solimando > Priority: Blocker > Fix For: 4.0.0-alpha-2 > > > The version of the scripts for _metastore_ and _standalone-metastore_ should > be in sync, but at the moment for the metastore side we are missing 3.2.0 > scripts (in _metastore/scripts/upgrade/hive_), while they are present in the > standalone_metastore counterpart(s): > * hive-schema-3.2.0.*.sql > * upgrade-3.1.0-to-3.2.0.*.sql > * upgrade-3.2.0-to-4.0.0-alpha-1.*.sql > * upgrade-4.0.0-alpha-1-to-4.0.0-alpha-2.*.sql -- This message was sent by Atlassian Jira (v8.20.1#820001)