[ 
https://issues.apache.org/jira/browse/DRILL-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507529#comment-14507529
 ] 

Daniel Barclay (Drill) commented on DRILL-2696:
-----------------------------------------------

> where does this cause problems in the course of query execution or other 
> drillbit operations?

Currently, it doesn't seem to, since we don't happen to use any resources with 
names that expose the bug.

It's a latent bug that I noticed while tracing through code and execution for 
something else.

> I get that the unit test is broken... 

I'm not sure what you mean (or how the current state or first-part patch 
appears).

I just created the unit test.  (It's not a pre-existing test.)

The test method that detects the bug is disabled with @Ignore because, since 
the bug seems to be a low-priority bug, my intent is to check in the unit test 
for future reference for whomever eventually addresses this bug, but of course 
I don't want the test to fail and break the build now.


> PathScanner.forResource(..., true, ...) breaks when URL-special character in 
> resource pathname
> ----------------------------------------------------------------------------------------------
>
>                 Key: DRILL-2696
>                 URL: https://issues.apache.org/jira/browse/DRILL-2696
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>            Reporter: Daniel Barclay (Drill)
>         Attachments: DRILL-2696-1Test.4.patch.txt, 
> DRILL-2696-1Test.5.patch.txt
>
>
> In class org.apache.drill.common.util.PathScanner, method forResource(...), 
> when called in return-classpath-root mode (with a value of true for parameter 
> stripName), breaks if the resource pathname contains any character that is 
> not represented by itself in a URL (e.g., ":", "%").  (The method returns the 
> resource URL rather than the requested corresponding classpath root URL.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to