[
https://issues.apache.org/jira/browse/DRILL-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045987#comment-15045987
]
ASF GitHub Bot commented on DRILL-4123:
---------------------------------------
Github user jaltekruse commented on the pull request:
https://github.com/apache/drill/pull/293#issuecomment-162704924
Apologies, didn't think about the order in which compilation and resolving
the injectables would be executed. I thought I had verified that this error
would make it back to users if the function was used in a select list, but
obviously there wasn't a test for it.
As far as looking at the output of explorers, the easiest way to do this
would be to use a function like maxdir in the where clause and then just
include dirN in the select clause as well. This will cause the function to be
evaluated just during pruning.
select dir0 from dfs.workspace`path/to/dir/*` where dir0 =
MAXDIR('dfs.workspace', '/path/to/dir');
> DirectoryExplorers should refer to fully qualified variable names
> -----------------------------------------------------------------
>
> Key: DRILL-4123
> URL: https://issues.apache.org/jira/browse/DRILL-4123
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Hanifi Gunes
> Assignee: Hanifi Gunes
>
> Execution fails with {code}CompileException: Line 75, Column 70: Unknown
> variable or type "FILE_SEPARATOR"{code} in case a directory explorer is used
> in a projection. Also FILE_SEPARATOR should not be platform dependent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
