Did some checking. The issue you have faced is only present if the DB version is 4.0.0, and we are running 4.0.0-alpha-1 code.
This will not happen if the user is using released Hive versions until they try to upgrade from 4.0.0-alpha-1 to 4.0.0-alpha-2, or 4.0.0. So I think we should not stop the release candidate for this. OTOH, this should be fixed for the next release, so I created the jira for it: https://issues.apache.org/jira/browse/HIVE-26062 <https://issues.apache.org/jira/browse/HIVE-26062> Thanks for testing! Peter > On 2022. Mar 23., at 10:30, dengzhhu653 <dengzhhu...@163.com> wrote: > > After I upgrade, the issue is gone. > > > +1 (non-binding) > * Rat check: ok > > - mvn clean apache-rat:check > * Build from source (1.8.0_312): ok > - mvn install -Pdist -DskipTests -Dmaven.javadoc.skip=true > > * Test simple queries on pseudo cluster with Hadoop 3.1.0(tez & mr), all good. > - create db,table/add,show partition... > - distinct + group by (1M rows) > * Checksums: ok > Thank you for pushing this forward! > > > Best, > Zhihua > At 2022-03-23 16:01:38, "Peter Vary" <pv...@cloudera.com.INVALID> wrote: >> I think you forgot to upgrade the metastore schema. >> We might want to provide a better error message. >> >>> On 2022. Mar 23., at 8:14, dengzhhu653 <dengzhhu...@163.com> wrote: >>> >>> >>> >>> >>> * Rat check: ok >>> - mvn clean apache-rat:check >>> * Build from source (1.8.0_312): ok >>> - mvn install -Pdist -DskipTests -Dmaven.javadoc.skip=true >>> * Test simple queries on pseudo cluster with Hadoop 3.1.0(tez & mr), but >>> failed to bring up the embedded metastore. >>> >>> >>> java.lang.NumberFormatException: For input string: "0-alpha-1" >>> at >>> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) >>> at java.lang.Integer.parseInt(Integer.java:580) >>> at java.lang.Integer.parseInt(Integer.java:615) >>> at >>> org.apache.hadoop.hive.metastore.MetaStoreSchemaInfo.isVersionCompatible(MetaStoreSchemaInfo.java:210) >>> at >>> org.apache.hadoop.hive.metastore.ObjectStore.checkSchema(ObjectStore.java:10870) >>> at >>> org.apache.hadoop.hive.metastore.ObjectStore.verifySchema(ObjectStore.java:10839) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:498) >>> at >>> org.apache.hadoop.hive.metastore.RawStoreProxy.invoke(RawStoreProxy.java:97) >>> at com.sun.proxy.$Proxy28.verifySchema(Unknown Source) >>> at >>> org.apache.hadoop.hive.metastore.HMSHandler.getMSForConf(HMSHandler.java:610) >>> at org.apache.hadoop.hive.metastore.HMSHandler.getMS(HMSHandler.java:602) >>> at >>> org.apache.hadoop.hive.metastore.HMSHandler.createDefaultDB(HMSHandler.java:686) >>> >>> >>> At 2022-03-23 01:22:40, "Stamatis Zampetakis" <zabe...@gmail.com> wrote: >>>> Hi Peter, >>>> >>>> Many thanks for rolling out the RC and for resolving many of the blocker >>>> issues that were remaining. >>>> >>>> In general, it is a good practice to include the commit hash (which tags >>>> the release) and the checksum hashes of the release artifacts [1] in the >>>> vote email to minimize the chances of man-in-the-middle attacks and voting >>>> on wrong packages. >>>> Can you please update this thread with those? >>>> >>>> Best, >>>> Stamatis >>>> >>>> [1] https://people.apache.org/~pvary/apache-hive-4.0.0-alpha-1-rc1/ >>>> >>>> >>>> On Tue, Mar 22, 2022 at 5:00 PM Naveen Gangam >>>> <ngan...@cloudera.com.invalid> >>>> wrote: >>>> >>>>> I have been able to build and run a quick test. I have NOT verified the >>>>> signature. I was trying to run the HMS Checkin tests and got this. I >>>>> suspect these are not specific to the alpha-1 branch. But it is not a test >>>>> failure (although it appears like it should be) >>>>> *"mvn test >>>>> >>>>> -Dtest.groups=org.apache.hadoop.hive.metastore.annotation.MetastoreCheckinTest"* >>>>> >>>>> [*INFO*] Running org.apache.hadoop.hive.common.metrics.*TestLegacyMetrics* >>>>> >>>>> [main] WARN org.apache.hadoop.hive.common.metrics.LegacyMetrics - Could >>>>> not >>>>> find counter value for foo.n, returning null instead. >>>>> >>>>> javax.management.AttributeNotFoundException: Key [foo.n] not found/tracked >>>>> >>>>> at >>>>> >>>>> org.apache.hadoop.hive.common.metrics.MetricsMBeanImpl.getAttribute(MetricsMBeanImpl.java:56) >>>>> >>>>> >>>>> [*WARNING*] *Tests **run: 18*, Failures: 0, Errors: 0, *Skipped: 2*, Time >>>>> elapsed: 4.158 s - in >>>>> org.apache.hadoop.hive.metastore.client.*TestCatalogs* >>>>> >>>>> [*INFO*] Running org.apache.hadoop.hive.metastore.*TestMarkPartition* >>>>> >>>>> [*INFO*] *Tests run: 1*, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >>>>> 15.021 s - in org.apache.hadoop.hive.metastore.*TestMarkPartition* >>>>> >>>>> [*INFO*] >>>>> >>>>> [*INFO*] Results: >>>>> >>>>> [*INFO*] >>>>> >>>>> [*WARNING*] *Tests run: 2182, Failures: 0, Errors: 0, Skipped: 5* >>>>> >>>>> >>>>> So over no test failures. >>>>> >>>>> +1 pending other votes (& non-binding) >>>>> >>>>> Thank you >>>>> Naveen >>>>> >>>>> On Tue, Mar 22, 2022 at 9:32 AM Marton Bod <m...@cloudera.com.invalid> >>>>> wrote: >>>>> >>>>>> +1 (non-binding) >>>>>> Tested the checksums, signatures and built it successfully >>>>>> >>>>>> On Tue, Mar 22, 2022 at 2:26 PM Peter Vary <pv...@cloudera.com.invalid> >>>>>> wrote: >>>>>> >>>>>>> Hi Team, >>>>>>> >>>>>>> Apache Hive 4.0.0-alpha-1 Release Candidate 1 is available here: >>>>>>> >>>>>>> https://people.apache.org/~pvary/apache-hive-4.0.0-alpha-1-rc1/ >>>>>>> >>>>>>> Maven artifacts are available here: >>>>>>> >>>>>>> https://repository.apache.org/content/repositories/orgapachehive-1111/ >>>>>>> >>>>>>> The tag 4.0.0-alpha-1-rc1 has been applied to the source for this >>>>> release >>>>>>> in github, you can see it at >>>>>>> https://github.com/apache/hive/tree/release-4.0.0-alpha-1-rc1 >>>>>>> >>>>>>> Voting will conclude in 72 hours. >>>>>>> >>>>>>> All interested parties: Please test. >>>>>>> Hive PMC Members: Please test and vote. >>>>>>> >>>>>>> Thanks. >>>>>> >>>>>
