Re: Review Request 37697: DRILL-3412: Projections are not getting push down below Window operator
On Aug. 22, 2015, 12:44 a.m., Aman Sinha wrote: Is there a reason to have this rule in Drill rather than in Calcite ? Jinfeng Ni wrote: Second this. Whenever possible, we should put rule in Calcite, especially it applies to LogicalProject/LogicalWindow. I see. I will send add this rule to calcite's master - Sean Hsuan-Yi --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37697/#review96106 --- On Aug. 21, 2015, 10:53 p.m., Sean Hsuan-Yi Chu wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37697/ --- (Updated Aug. 21, 2015, 10:53 p.m.) Review request for drill and Aman Sinha. Bugs: DRILL-3412 https://issues.apache.org/jira/browse/DRILL-3412 Repository: drill-git Description --- DrillPushProjectPastWindowRule to push Project past Window Diffs - exec/java-exec/src/main/java/org/apache/drill/exec/planner/logical/DrillPushProjectPastWindowRule.java PRE-CREATION exec/java-exec/src/main/java/org/apache/drill/exec/planner/logical/DrillRuleSets.java 4307757 exec/java-exec/src/main/java/org/apache/drill/exec/planner/physical/visitor/InsertLocalExchangeVisitor.java ad64ed8 exec/java-exec/src/test/java/org/apache/drill/exec/TestWindowFunctions.java 29b702c Diff: https://reviews.apache.org/r/37697/diff/ Testing --- all required Thanks, Sean Hsuan-Yi Chu
[jira] [Created] (DRILL-3686) no-ZooKeeper logging: Curator messages not in main file, no trying ZooKeeper from Drill
Daniel Barclay (Drill) created DRILL-3686: - Summary: no-ZooKeeper logging: Curator messages not in main file, no trying ZooKeeper from Drill Key: DRILL-3686 URL: https://issues.apache.org/jira/browse/DRILL-3686 Project: Apache Drill Issue Type: Bug Reporter: Daniel Barclay (Drill) When Drill is started when ZooKeeper is not running, the logging could be clearer. The log messages from Curator (e.g., ERROR org.apache.curator.ConnectionState - Connection timed out for connection string (localhost:2181) and timeout (5000) / elapsed (5568)) don't go to Drill's normal/main log file .../drillbit.log; instead they go to .../Drillbit.out. (They'd be easier to notice and find if they were in the main log file where most of the rest of Drill's logging output is.) Additionally, at least at the default logging level (for drillbit.sh), nothing in the main log says that Drill's about to try to connect to ZooKeeper. (Seeing a connecting to ZooKeeper message without a following connected to ZooKeeper message) in the main log would help point the reader to the secondary log, even if we can't/don't get the Curator log output into the main log file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3685) Failure to execute query with NTILE and ROW_NUMBER window functions with different window definitions
Victoria Markman created DRILL-3685:
---
Summary: Failure to execute query with NTILE and ROW_NUMBER window
functions with different window definitions
Key: DRILL-3685
URL: https://issues.apache.org/jira/browse/DRILL-3685
Project: Apache Drill
Issue Type: Bug
Components: Execution - Data Types
Affects Versions: 1.2.0
Reporter: Victoria Markman
Assignee: Hanifi Gunes
{code}
0: jdbc:drill:schema=dfs select
. . . . . . . . . . . . c_integer,
. . . . . . . . . . . . row_number() over (order by c_date desc),
. . . . . . . . . . . . ntile(100) over (order by c_date,
c_timestamp )
. . . . . . . . . . . . from
. . . . . . . . . . . . j2
. . . . . . . . . . . . ;
Error: SYSTEM ERROR: UnsupportedOperationException: Unable to get value vector
class for minor type [LATE] and mode [OPTIONAL]
Fragment 0:0
[Error Id: 1912dd81-dda4-4576-9bd9-420189ff57fe on atsqa4-133.qa.lab:31010]
(state=,code=0)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] drill pull request: fix missing indirect dependency
Github user aleph-zero commented on the pull request: https://github.com/apache/drill/pull/121#issuecomment-133504816 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] drill pull request: remove deprecated constructor and related test...
GitHub user julienledem opened a pull request: https://github.com/apache/drill/pull/125 remove deprecated constructor and related test code duplication You can merge this pull request into a Git repository by running: $ git pull https://github.com/julienledem/drill cleanup_tests Alternatively you can review and apply these changes as the patch at: https://github.com/apache/drill/pull/125.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #125 commit 562a03a0a80097f89ad6a9eb027f6af15a58c812 Author: Julien Le Dem jul...@ledem.net Date: 2015-08-21T17:56:55Z remove deprecated constructor and related test code duplication --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (DRILL-3684) CTAS : Memory Leak when using CTAS with tpch sf100
Rahul Challapalli created DRILL-3684:
Summary: CTAS : Memory Leak when using CTAS with tpch sf100
Key: DRILL-3684
URL: https://issues.apache.org/jira/browse/DRILL-3684
Project: Apache Drill
Issue Type: Bug
Components: Storage - Parquet
Reporter: Rahul Challapalli
Assignee: Steven Phillips
git.commit.id.abbrev=55dfd0e
Below is the sequence of operations which resulted in the issue. The input to
the CTAS is the lineitem table from Tpch SF100 data set
{code}
ALTER SESSION SET `store.parquet.block-size` = 103;
create table lineitem as select * from dfs.`/drill/testdata/tpch100/lineitem`;
java.sql.SQLException: SYSTEM ERROR: IllegalStateException: Attempted to close
accountor with 2 buffer(s) still allocatedfor QueryId:
2a28b5d1-08f4-cdc6-0287-d8714b8ab713, MajorFragmentId: 1, MinorFragmentId: 10.
Total 2 allocation(s) of byte size(s): 65536, 65536, at stack location:
org.apache.drill.exec.memory.TopLevelAllocator$ChildAllocator.buffer(TopLevelAllocator.java:266)
org.apache.drill.exec.store.parquet.ParquetDirectByteBufferAllocator.allocate(ParquetDirectByteBufferAllocator.java:51)
parquet.bytes.CapacityByteArrayOutputStream.allocateSlab(CapacityByteArrayOutputStream.java:69)
parquet.bytes.CapacityByteArrayOutputStream.initSlabs(CapacityByteArrayOutputStream.java:85)
parquet.bytes.CapacityByteArrayOutputStream.init(CapacityByteArrayOutputStream.java:64)
parquet.column.values.rle.RunLengthBitPackingHybridEncoder.init(RunLengthBitPackingHybridEncoder.java:132)
parquet.column.values.rle.RunLengthBitPackingHybridValuesWriter.init(RunLengthBitPackingHybridValuesWriter.java:41)
parquet.column.ParquetProperties.getColumnDescriptorValuesWriter(ParquetProperties.java:96)
parquet.column.impl.ColumnWriterV1.init(ColumnWriterV1.java:76)
parquet.column.impl.ColumnWriteStoreV1.newMemColumn(ColumnWriteStoreV1.java:70)
parquet.column.impl.ColumnWriteStoreV1.getColumnWriter(ColumnWriteStoreV1.java:58)
parquet.io.MessageColumnIO$MessageColumnIORecordConsumer.init(MessageColumnIO.java:183)
parquet.io.MessageColumnIO.getRecordWriter(MessageColumnIO.java:375)
org.apache.drill.exec.store.parquet.ParquetRecordWriter.newSchema(ParquetRecordWriter.java:193)
org.apache.drill.exec.store.parquet.ParquetRecordWriter.checkBlockSizeReached(ParquetRecordWriter.java:267)
org.apache.drill.exec.store.parquet.ParquetRecordWriter.endRecord(ParquetRecordWriter.java:361)
org.apache.drill.exec.store.EventBasedRecordWriter.write(EventBasedRecordWriter.java:64)
org.apache.drill.exec.physical.impl.WriterRecordBatch.innerNext(WriterRecordBatch.java:106)
org.apache.drill.exec.record.AbstractRecordBatch.next(AbstractRecordBatch.java:147)
org.apache.drill.exec.physical.impl.validate.IteratorValidatorBatchIterator.next(IteratorValidatorBatchIterator.java:118)
org.apache.drill.exec.physical.impl.BaseRootExec.next(BaseRootExec.java:83)
org.apache.drill.exec.physical.impl.SingleSenderCreator$SingleSenderRootExec.innerNext(SingleSenderCreator.java:95)
org.apache.drill.exec.physical.impl.BaseRootExec.next(BaseRootExec.java:73)
org.apache.drill.exec.work.fragment.FragmentExecutor$1.run(FragmentExecutor.java:258)
org.apache.drill.exec.work.fragment.FragmentExecutor$1.run(FragmentExecutor.java:252)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAs(Subject.java:415)
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1566)
org.apache.drill.exec.work.fragment.FragmentExecutor.run(FragmentExecutor.java:252)
org.apache.drill.common.SelfCleaningRunnable.run(SelfCleaningRunnable.java:38)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
java.lang.Thread.run(Thread.java:745)
Fragment 1:10
[Error Id: 6198bce1-d1fd-46b9-b211-2c7547f489c0 on qa-node191.qa.lab:31010]
Aborting command set because force is false and command failed: create table
lineitem as select * from dfs.`/drill/testdata/tpch100/lineitem`;
{code}
Attached the log file required. The data is too large to upload it here
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DRILL-3687) NullPointerException from query with WITH, VALUES, and USING
Daniel Barclay (Drill) created DRILL-3687:
-
Summary: NullPointerException from query with WITH, VALUES, and
USING
Key: DRILL-3687
URL: https://issues.apache.org/jira/browse/DRILL-3687
Project: Apache Drill
Issue Type: Bug
Reporter: Daniel Barclay (Drill)
The following query fails:
{noformat}
WITH q(key) AS (VALUES 1, 1) SELECT * FROM q q1 INNER JOIN q q2 USING (key)
{noformat}
The failures is a NullPointerException SYSTEM ERROR message:
{noformat}
Error: SYSTEM ERROR: NullPointerException
[Error Id: ba74e744-7c8a-4ec8-b046-ac28ad0a03a4 on dev-linux2:31010]
(state=,code=0)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DRILL-3688) Drill should honor skip.header.line.count attribute of Hive table
Hao Zhu created DRILL-3688:
--
Summary: Drill should honor skip.header.line.count attribute of
Hive table
Key: DRILL-3688
URL: https://issues.apache.org/jira/browse/DRILL-3688
Project: Apache Drill
Issue Type: Bug
Components: Query Planning Optimization
Affects Versions: 1.1.0
Environment: 1.1
Reporter: Hao Zhu
Assignee: Jinfeng Ni
Currently Drill does not honor the skip.header.line.count attribute of Hive
table.
It may cause some other format conversion issue.
Reproduce:
1. Create a Hive table
{code}
create table h1db.testheader(col0 string)
ROW FORMAT DELIMITED FIELDS TERMINATED BY '|'
STORED AS TEXTFILE
tblproperties(skip.header.line.count=1);
{code}
2. Prepare a sample data:
{code}
# cat test.data
col0
2015-01-01
{code}
3. Load sample data into Hive
{code}
LOAD DATA LOCAL INPATH '/xxx/test.data' OVERWRITE INTO TABLE h1db.testheader;
{code}
4. Hive
{code}
hive select * from h1db.testheader ;
OK
2015-01-01
Time taken: 0.254 seconds, Fetched: 1 row(s)
{code}
5. Drill
{code}
select * from hive.h1db.testheader ;
+-+
|col0 |
+-+
| col0|
| 2015-01-01 |
+-+
2 rows selected (0.257 seconds)
select cast(col0 as date) from hive.h1db.testheader ;
Error: SYSTEM ERROR: IllegalFieldValueException: Value 0 for monthOfYear must
be in the range [1,12]
Fragment 0:0
[Error Id: 34353702-ca27-440b-a4f4-0c9f79fc8ccd on h1.poc.com:31010]
(org.joda.time.IllegalFieldValueException) Value 0 for monthOfYear must be in
the range [1,12]
org.joda.time.field.FieldUtils.verifyValueBounds():236
org.joda.time.chrono.BasicChronology.getDateMidnightMillis():613
org.joda.time.chrono.BasicChronology.getDateTimeMillis():159
org.joda.time.chrono.AssembledChronology.getDateTimeMillis():120
org.apache.drill.exec.expr.fn.impl.StringFunctionHelpers.memGetDate():261
org.apache.drill.exec.expr.fn.impl.StringFunctionHelpers.getDate():218
org.apache.drill.exec.test.generated.ProjectorGen0.doEval():67
org.apache.drill.exec.test.generated.ProjectorGen0.projectRecords():62
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.doWork():172
org.apache.drill.exec.record.AbstractSingleRecordBatch.innerNext():93
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.innerNext():129
org.apache.drill.exec.record.AbstractRecordBatch.next():147
org.apache.drill.exec.physical.impl.BaseRootExec.next():83
org.apache.drill.exec.physical.impl.ScreenCreator$ScreenRoot.innerNext():79
org.apache.drill.exec.physical.impl.BaseRootExec.next():73
org.apache.drill.exec.work.fragment.FragmentExecutor$1.run():261
org.apache.drill.exec.work.fragment.FragmentExecutor$1.run():255
java.security.AccessController.doPrivileged():-2
javax.security.auth.Subject.doAs():422
org.apache.hadoop.security.UserGroupInformation.doAs():1566
org.apache.drill.exec.work.fragment.FragmentExecutor.run():255
org.apache.drill.common.SelfCleaningRunnable.run():38
java.util.concurrent.ThreadPoolExecutor.runWorker():1142
java.util.concurrent.ThreadPoolExecutor$Worker.run():617
java.lang.Thread.run():745 (state=,code=0)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[Apache Drill] Creating Views
Hi Devs, I was trying to create views on top of my mongo datasource recently so that I can use them from BI tools. I was wondering if there is a rest api to create the views programmatically . Actually the use case I was thinking that I will use the rest api to configure the FS workspace for the schema and I will start creating the views from a program.. Could you clarify this part for me please. Thanks, Sudip ***Legal Disclaimer*** This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you. **
[GitHub] drill pull request: Calcite1.4.0 rebase
GitHub user jinfengni opened a pull request: https://github.com/apache/drill/pull/126 Calcite1.4.0 rebase The Drill's forked version, after rebasing on today's Calcite 1.4.0 master branch, is currently located here: https://github.com/jinfengni/incubator-optiq/tree/DrillCalcite1.4.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jinfengni/incubator-drill Calcite1.4.0Rebase Alternatively you can review and apply these changes as the patch at: https://github.com/apache/drill/pull/126.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #126 commit 289d35251f71524d467b9678fe34bdcfcf05e9ab Author: Jinfeng Ni j...@apache.org Date: 2015-07-28T23:23:04Z DRILL-3542: Rebase Drill on Calcite 1.4.0 release. Changes includes: - Parser configuration change - Rule name change. - Consistency checking in SqlOperator. - Exclude dependency inherited from Calcite, due to version conflicts. commit b0a32da29521e986d8044ac3a8e04a3e681602be Author: Jinfeng Ni j...@apache.org Date: 2015-08-04T08:54:40Z DRILL-3542: Add method to use both field names and types to determine project operator's triviality. [CALCITE-577] removes a deprecated code where project operator's triviality depends both names and types. Drill has to add it back, since field name matters in Drill's execution engine. commit cb41819334eef8d1cca593ad654afaf5261db97c Author: Jinfeng Ni j...@apache.org Date: 2015-08-06T00:51:05Z DRILL-3542: Distinct aggregate expansion should convert to join. Add JoinPushExpressionRule. The changes are result of CALCITE-732 and CALCITE-850. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Review Request 37697: DRILL-3412: Projections are not getting push down below Window operator
On Aug. 21, 2015, 5:44 p.m., Aman Sinha wrote: Is there a reason to have this rule in Drill rather than in Calcite ? Second this. Whenever possible, we should put rule in Calcite, especially it applies to LogicalProject/LogicalWindow. - Jinfeng --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37697/#review96106 --- On Aug. 21, 2015, 3:53 p.m., Sean Hsuan-Yi Chu wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37697/ --- (Updated Aug. 21, 2015, 3:53 p.m.) Review request for drill and Aman Sinha. Bugs: DRILL-3412 https://issues.apache.org/jira/browse/DRILL-3412 Repository: drill-git Description --- DrillPushProjectPastWindowRule to push Project past Window Diffs - exec/java-exec/src/main/java/org/apache/drill/exec/planner/logical/DrillPushProjectPastWindowRule.java PRE-CREATION exec/java-exec/src/main/java/org/apache/drill/exec/planner/logical/DrillRuleSets.java 4307757 exec/java-exec/src/main/java/org/apache/drill/exec/planner/physical/visitor/InsertLocalExchangeVisitor.java ad64ed8 exec/java-exec/src/test/java/org/apache/drill/exec/TestWindowFunctions.java 29b702c Diff: https://reviews.apache.org/r/37697/diff/ Testing --- all required Thanks, Sean Hsuan-Yi Chu
[jira] [Created] (DRILL-3689) incorrect results : aggregate AVG returns wrong results over results returned by LEAD function.
Khurram Faraaz created DRILL-3689:
-
Summary: incorrect results : aggregate AVG returns wrong results
over results returned by LEAD function.
Key: DRILL-3689
URL: https://issues.apache.org/jira/browse/DRILL-3689
Project: Apache Drill
Issue Type: Bug
Components: Execution - Flow
Affects Versions: 1.2.0
Environment: private-branch
https://github.com/adeneche/incubator-drill/tree/new-window-funcs
Reporter: Khurram Faraaz
Assignee: Chris Westin
Priority: Critical
Aggregate AVG returns wrong results over results returned by LEAD function.
results returned by Drill
{code}
0: jdbc:drill:schema=dfs.tmp SELECT avg(lead_col1) FROM (SELECT LEAD(col1)
OVER(PARTITION BY col7 ORDER BY col1) lead_col1 , col7 FROM FEWRWSPQQ_101)
sub_query;
+-+
| EXPR$0 |
+-+
| 2.35195986941647008E17 |
+-+
1 row selected (0.264 seconds)
{code}
Explain plan for above query from Drill
{code}
0: jdbc:drill:schema=dfs.tmp explain plan for SELECT avg(lead_col1) FROM
(SELECT LEAD(col1) OVER(PARTITION BY col7 ORDER BY col1) lead_col1 , col7 FROM
FEWRWSPQQ_101) sub_query;
+--+--+
| text | json |
+--+--+
| 00-00Screen
00-01 Project(EXPR$0=[$0])
00-02Project(EXPR$0=[CAST(/(CastHigh(CASE(=($1, 0), null, $0)),
$1)):ANY NOT NULL])
00-03 StreamAgg(group=[{}], agg#0=[$SUM0($0)], agg#1=[COUNT($0)])
00-04Project(w0$o0=[$3])
00-05 Window(window#0=[window(partition {2} order by [1] range
between UNBOUNDED PRECEDING and CURRENT ROW aggs [LEAD($1)])])
00-06SelectionVectorRemover
00-07 Sort(sort0=[$2], sort1=[$1], dir0=[ASC], dir1=[ASC])
00-08Project(T36¦¦*=[$0], col1=[$1], col7=[$2])
00-09 Scan(groupscan=[ParquetGroupScan
[entries=[ReadEntryWithPath [path=maprfs:///tmp/FEWRWSPQQ_101]],
selectionRoot=maprfs:/tmp/FEWRWSPQQ_101, numFiles=1, columns=[`*`]]])
{code}
results returned by Postgres
{code}
postgres=# SELECT avg(lead_col1) FROM (SELECT LEAD(col1) OVER(PARTITION BY
col7 ORDER BY col1) lead_col1 , col7 FROM FEWRWSPQQ_101) sub_query;
avg
-
1157533190627124568
(1 row)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] drill pull request: Calcite1.4.0 rebase
Github user jinfengni closed the pull request at: https://github.com/apache/drill/pull/126 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Review Request 37697: DRILL-3412: Projections are not getting push down below Window operator
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37697/#review96106 --- Is there a reason to have this rule in Drill rather than in Calcite ? - Aman Sinha On Aug. 21, 2015, 10:53 p.m., Sean Hsuan-Yi Chu wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37697/ --- (Updated Aug. 21, 2015, 10:53 p.m.) Review request for drill and Aman Sinha. Bugs: DRILL-3412 https://issues.apache.org/jira/browse/DRILL-3412 Repository: drill-git Description --- DrillPushProjectPastWindowRule to push Project past Window Diffs - exec/java-exec/src/main/java/org/apache/drill/exec/planner/logical/DrillPushProjectPastWindowRule.java PRE-CREATION exec/java-exec/src/main/java/org/apache/drill/exec/planner/logical/DrillRuleSets.java 4307757 exec/java-exec/src/main/java/org/apache/drill/exec/planner/physical/visitor/InsertLocalExchangeVisitor.java ad64ed8 exec/java-exec/src/test/java/org/apache/drill/exec/TestWindowFunctions.java 29b702c Diff: https://reviews.apache.org/r/37697/diff/ Testing --- all required Thanks, Sean Hsuan-Yi Chu
[jira] [Resolved] (DRILL-2312) JDBC driver returning incorrect data after extended usage
[
https://issues.apache.org/jira/browse/DRILL-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Barclay (Drill) resolved DRILL-2312.
---
Resolution: Cannot Reproduce
Closing because attempts to reproduce this now on Drill pre-1.2 have failed and
this bug was reported way back on version 0.7.
JDBC driver returning incorrect data after extended usage
-
Key: DRILL-2312
URL: https://issues.apache.org/jira/browse/DRILL-2312
Project: Apache Drill
Issue Type: Bug
Components: Client - JDBC
Reporter: Norris Lee
Assignee: Daniel Barclay (Drill)
Fix For: 1.2.0
After executing ~20-30 queries with the JDBC driver, the data returned from a
Show files query is incorrect, particularly the isFile and isDirectory
columns. The first item in the schema/directory will be correct, but
subsequent items will report false for isFile and isDirectory.
This was tested with just a simple program that just loops through
executeQuery and prints out the values for isFile and isDirectory. The JDBC
driver used was the Drill 0.7 snapshot.
{code}
isFile: true
isDirectory: false
isFile: false
isDirectory: false
isFile: false
isDirectory: false
isFile: false
isDirectory: false
isFile: false
isDirectory: false
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
