You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Raghav Aggarwal (Jira)" <ji...@apache.org> on 2024/03/29 08:25:00 UTC
[jira] [Updated] (HIVE-28163) Upgrade apache directory server to 2.0.0-M24
[ https://issues.apache.org/jira/browse/HIVE-28163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghav Aggarwal updated HIVE-28163:
-----------------------------------
Description:
The reason for the update is that the 1.5.7 version is not compatible with jdk17. If we move hive to jdk 17, there are test failures because of the apache directory server version
Here is the failing test case:
{code:java}
mvn test -Dtest=org.apache.hive.service.auth.TestLdapAtnProviderWithMiniDS#testUserAndGroupFilterPositive{code}
Here is the stacktrace:
{code:java}
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.943 s <<< FAILURE! - in org.apache.hive.service.auth.TestLdapAtnProviderWithMiniDS[ERROR] org.apache.hive.service.auth.TestLdapAtnProviderWithMiniDS Time elapsed: 4.941 s <<< ERROR!java.lang.ExceptionInInitializerErrorat org.apache.directory.server.core.partition.ldif.LdifPartition.getOSFileName(LdifPartition.java:630)at org.apache.directory.server.core.partition.ldif.LdifPartition.getFileName(LdifPartition.java:621)at org.apache.directory.server.core.partition.ldif.LdifPartition.doInit(LdifPartition.java:187)at org.apache.directory.server.core.partition.AbstractPartition.initialize(AbstractPartition.java:65)at org.apache.directory.server.core.schema.SchemaPartition.doInit(SchemaPartition.java:229)at org.apache.directory.server.core.partition.AbstractPartition.initialize(AbstractPartition.java:65)at org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:1426)at org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:907)at org.apache.directory.server.core.factory.DefaultDirectoryServiceFactory.build(DefaultDirectoryServiceFactory.java:215)at org.apache.directory.server.core.factory.DefaultDirectoryServiceFactory.init(DefaultDirectoryServiceFactory.java:114)at org.apache.directory.server.core.factory.DSAnnotationProcessor.createDS(DSAnnotationProcessor.java:85)at org.apache.directory.server.core.factory.DSAnnotationProcessor.getDirectoryService(DSAnnotationProcessor.java:174)at org.apache.directory.server.core.integ.FrameworkRunner.run(FrameworkRunner.java:107)at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379)at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340)at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413)Caused by: java.lang.NumberFormatException: multiple pointsat java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1914)at java.base/jdk.internal.math.FloatingDecimal.parseFloat(FloatingDecimal.java:122)at java.base/java.lang.Float.parseFloat(Float.java:476)at org.apache.directory.shared.ldap.util.SystemUtils.getJavaVersionAsFloat(SystemUtils.java:1336)at org.apache.directory.shared.ldap.util.SystemUtils.<clinit>(SystemUtils.java:944)... 21 more {code}
was:The reason for the update is that the 1.5.7 version is not compatible with jdk17. If we move hive to jdk 17, there are test failures because of the apache directory server version
> Upgrade apache directory server to 2.0.0-M24
> --------------------------------------------
>
> Key: HIVE-28163
> URL: https://issues.apache.org/jira/browse/HIVE-28163
> Project: Hive
> Issue Type: Improvement
> Reporter: Raghav Aggarwal
> Assignee: Raghav Aggarwal
> Priority: Major
>
> The reason for the update is that the 1.5.7 version is not compatible with jdk17. If we move hive to jdk 17, there are test failures because of the apache directory server version
> Here is the failing test case:
> {code:java}
> mvn test -Dtest=org.apache.hive.service.auth.TestLdapAtnProviderWithMiniDS#testUserAndGroupFilterPositive{code}
>
> Here is the stacktrace:
> {code:java}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.943 s <<< FAILURE! - in org.apache.hive.service.auth.TestLdapAtnProviderWithMiniDS[ERROR] org.apache.hive.service.auth.TestLdapAtnProviderWithMiniDS Time elapsed: 4.941 s <<< ERROR!java.lang.ExceptionInInitializerErrorat org.apache.directory.server.core.partition.ldif.LdifPartition.getOSFileName(LdifPartition.java:630)at org.apache.directory.server.core.partition.ldif.LdifPartition.getFileName(LdifPartition.java:621)at org.apache.directory.server.core.partition.ldif.LdifPartition.doInit(LdifPartition.java:187)at org.apache.directory.server.core.partition.AbstractPartition.initialize(AbstractPartition.java:65)at org.apache.directory.server.core.schema.SchemaPartition.doInit(SchemaPartition.java:229)at org.apache.directory.server.core.partition.AbstractPartition.initialize(AbstractPartition.java:65)at org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:1426)at org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:907)at org.apache.directory.server.core.factory.DefaultDirectoryServiceFactory.build(DefaultDirectoryServiceFactory.java:215)at org.apache.directory.server.core.factory.DefaultDirectoryServiceFactory.init(DefaultDirectoryServiceFactory.java:114)at org.apache.directory.server.core.factory.DSAnnotationProcessor.createDS(DSAnnotationProcessor.java:85)at org.apache.directory.server.core.factory.DSAnnotationProcessor.getDirectoryService(DSAnnotationProcessor.java:174)at org.apache.directory.server.core.integ.FrameworkRunner.run(FrameworkRunner.java:107)at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379)at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340)at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413)Caused by: java.lang.NumberFormatException: multiple pointsat java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1914)at java.base/jdk.internal.math.FloatingDecimal.parseFloat(FloatingDecimal.java:122)at java.base/java.lang.Float.parseFloat(Float.java:476)at org.apache.directory.shared.ldap.util.SystemUtils.getJavaVersionAsFloat(SystemUtils.java:1336)at org.apache.directory.shared.ldap.util.SystemUtils.<clinit>(SystemUtils.java:944)... 21 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)