[
https://issues.apache.org/jira/browse/HIVE-22490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985259#comment-16985259
]
Hive QA commented on HIVE-22490:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12987170/HIVE-22490.1.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 17753 tests
executed
*Failed tests:*
{noformat}
org.apache.hive.jdbc.TestSSL.testMetastoreConnectionWrongCertCN (batchId=285)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/19685/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/19685/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-19685/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12987170 - PreCommit-HIVE-Build
> Adding jars with special characters in their path throws error
> --------------------------------------------------------------
>
> Key: HIVE-22490
> URL: https://issues.apache.org/jira/browse/HIVE-22490
> Project: Hive
> Issue Type: Bug
> Reporter: Ádám Szita
> Assignee: Ádám Szita
> Priority: Major
> Attachments: HIVE-22490.0.patch, HIVE-22490.1.patch
>
>
> HIVE-9664 introduced a change that uses URIs in SessionState to handle adding
> jars or other dependencies in a Hive session, but neglects to handle URIs as
> actual URIs, i.e. calling toString() on them.
> This resulted in a regression as a path such as /tmp/blabla-[special].jar was
> working before HIVE-9664 and now it's throwing a URISyntaxException error.
> I think it's fair to make the users provide an URL which is encoded
> ({{blabla-%5Bspecial%5D.jar)}}, but then the issue of the current
> implementation will be the inability to find the file on FS, because Hive
> will look for it in {{blabla-%5Bspecial%5D.jar}} format, instead of
> blabla-[special].jar.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)