[
https://issues.apache.org/jira/browse/DRILL-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227236#comment-14227236
]
Mehant Baid commented on DRILL-1488:
------------------------------------
Changes looks good.
I had a question about
DrillParserWithCompoundIdConverter.IDENTIFIER_MAX_LENGTH. Will it be thread
safe logic to set this in DrillSqlWorker? If we have two sessions connecting to
the same DrillBit and executing queries then we will have two Foreman's
manipulating this variable without synchronization?
> Limit on file name in sql query is too small
> --------------------------------------------
>
> Key: DRILL-1488
> URL: https://issues.apache.org/jira/browse/DRILL-1488
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Parth Chandra
> Assignee: Mehant Baid
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments:
> 0001-DRILL-1488-Provide-configurable-option-to-set-the-sq.patch
>
>
> While building from the release tarball, unit test fail if you build from a
> directory that is nested several levels deep such that the full path to some
> of the test data files is longer than 128 characters.
> The limit appears to be very small and should be increased.
> One of the errors during the build that illustrates the problem:
> testTextJoin(org.apache.drill.TestExampleQueries) Time elapsed: 0.011 sec
> <<< ERROR!
> org.apache.drill.exec.rpc.RpcException: Failure while parsing sql. Length of
> identifier
> 'file:/Users/pchandra/work/drill-release/apache-drill-0.6.0-incubating-src/exec/java-exec/target/test-classes/store/text/data/nations.csv'
> must be less than or equal to 128 characters
> [38933037-d38d-4278-a215-b722cc97811c]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
