Re: [VOTE] Release Apache Drill 1.5.0 RC3

[Jacques Nadeau]

Download, build, unit tests.
Deploy on small cluster and verify operation of a few distributed queries.

LGTM
+1 (binding)

--
Jacques Nadeau
CTO and Co-Founder, Dremio

On Thu, Feb 11, 2016 at 4:18 PM, rahul challapalli <
challapallira...@gmail.com> wrote:

> +1 (non-binding)
>
> Built from source and ran the Functional and Advanced suites from the test
> framework.
> Performed some sanity tests against web ui authentication.
>
> On Thu, Feb 11, 2016 at 4:03 PM, Jason Altekruse  >
> wrote:
>
> > Thanks for the vote Sudheesh!
> >
> > Please, others with time available try out the candidate, the vote is
> > supposed to close tomorrow at 7PM Pacific.
> >
> > Thanks,
> > Jason
> >
> > On Thu, Feb 11, 2016 at 3:53 PM, Sudheesh Katkam 
> > wrote:
> >
> > > +1 (non-binding; committer)
> > >
> > > * downloaded and built from source tar-ball; ran unit tests
> successfully
> > on
> > > Ubuntu
> > > * ran simple queries (including cancellations) in embedded mode on Mac;
> > > verified states in web UI
> > > * ran simple queries (including cancellations) on a 3 node cluster;
> > > verified states in web UI
> > > * verified that queries complete with queuing enabled
> > > * verified md5 and sha1 checksums on binary and src tar-balls, and
> zipped
> > > folder
> > >
> > > Thank you,
> > > Sudheesh
> > >
> > > On Tue, Feb 9, 2016 at 7:38 PM, Jason Altekruse <
> > altekruseja...@gmail.com>
> > > wrote:
> > >
> > > > For anyone who jumped on testing out the release candidate early I'm
> > > going
> > > > to have to ask you to re-download the artifacts you verified. I had
> > > > prepared an earlier version of this candidate (but didn't get a
> chance
> > to
> > > > start the vote) before another regression was identified and fixed
> > > today. I
> > > > had forgotten to update the source and binary artifacts on my apache
> > web
> > > > space with the new ones.
> > > >
> > > > I just uploaded the corrected versions of the artifacts after
> verifying
> > > > their git.properties files to ensure they were the correct versions.
> > > >
> > > > The last modified dates on the correct versions are between:
> > 10-Feb-2016
> > > > 03:30 and 10-Feb-2016 03:34
> > > >
> > > > (the copy took a few minutes as my home upload speed isn't great :P)
> > > >
> > > > Sorry about the mistake, everything should be good to go now.
> > > >
> > > > Thanks,
> > > > Jason
> > > >
> > > >
> > > >
> > > > On Tue, Feb 9, 2016 at 7:08 PM, Jason Altekruse <
> > > altekruseja...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello all,
> > > > >
> > > > > I'd like to propose the forth release candidate (rc3) of Apache
> > Drill,
> > > > > version
> > > > > 1.5.0. It covers a total of 60 resolved JIRAs [1]. Thanks to
> everyone
> > > who
> > > > > contributed to this release. This release candidate includes fixes
> > for
> > > > > DRILL-4235 and DRILL-4380, both regressions found sine the last
> > release
> > > > > candidate.
> > > > >
> > > > > I also pulled in two bug fixes (4230, 4349) that had been merged
> into
> > > > > master since making the release branch, they looked useful to
> include
> > > and
> > > > > were both had little risk of introducing regressions.
> > > > >
> > > > > The tarball artifacts are hosted at [2] and the maven artifacts are
> > > > hosted
> > > > > at
> > > > > [3]. This release candidate is based on commit
> > > > > 3f228d34782741457a14e28b0d1fdbc35a4fd958 located at [4].
> > > > >
> > > > > The vote will be open for the next 72 hours ending at 7 PM Pacific,
> > > > > February 12th, 2016.
> > > > >
> > > > > [ ] +1
> > > > > [ ] +0
> > > > > [ ] -1
> > > > >
> > > > > Here's my vote: +1
> > > > >
> > > > > Thanks,
> > > > > Jason
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12332948
> > > > >
> > > > > [2] http://people.apache.org/~json/apache-drill-1.5.0.rc3/
> > > > > [3]
> > > >
> https://repository.apache.org/content/repositories/orgapachedrill-1028
> > > > > [4]
> > https://github.com/jaltekruse/incubator-drill/tree/drill-1.5.0-rc3
> > > > >
> > > >
> > >
> >
>

[GitHub] drill pull request: DRILL-3623: Optimize limit 0 queries

[StevenMPhillips]

Github user StevenMPhillips commented on the pull request:

https://github.com/apache/drill/pull/364#issuecomment-183008840
  
@hhsuanyi I did not open any calcite jira. The new calcite version was 
there from Sudheesh's commit which I pulled in.

@sudheeshkatkam Does your update handle limit 0 for all types?



---
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: DRILL-4091: Support for additional gis operati...

[k255]

Github user k255 commented on the pull request:

https://github.com/apache/drill/pull/258#issuecomment-182857803
  
Aggregate version of st_union allows merging geometries using 'group by'


---
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: [VOTE] Release Apache Drill 1.5.0 RC3

[Jason Altekruse]

Thanks for the vote Sudheesh!

Please, others with time available try out the candidate, the vote is
supposed to close tomorrow at 7PM Pacific.

Thanks,
Jason

On Thu, Feb 11, 2016 at 3:53 PM, Sudheesh Katkam 
wrote:

> +1 (non-binding; committer)
>
> * downloaded and built from source tar-ball; ran unit tests successfully on
> Ubuntu
> * ran simple queries (including cancellations) in embedded mode on Mac;
> verified states in web UI
> * ran simple queries (including cancellations) on a 3 node cluster;
> verified states in web UI
> * verified that queries complete with queuing enabled
> * verified md5 and sha1 checksums on binary and src tar-balls, and zipped
> folder
>
> Thank you,
> Sudheesh
>
> On Tue, Feb 9, 2016 at 7:38 PM, Jason Altekruse 
> wrote:
>
> > For anyone who jumped on testing out the release candidate early I'm
> going
> > to have to ask you to re-download the artifacts you verified. I had
> > prepared an earlier version of this candidate (but didn't get a chance to
> > start the vote) before another regression was identified and fixed
> today. I
> > had forgotten to update the source and binary artifacts on my apache web
> > space with the new ones.
> >
> > I just uploaded the corrected versions of the artifacts after verifying
> > their git.properties files to ensure they were the correct versions.
> >
> > The last modified dates on the correct versions are between: 10-Feb-2016
> > 03:30 and 10-Feb-2016 03:34
> >
> > (the copy took a few minutes as my home upload speed isn't great :P)
> >
> > Sorry about the mistake, everything should be good to go now.
> >
> > Thanks,
> > Jason
> >
> >
> >
> > On Tue, Feb 9, 2016 at 7:08 PM, Jason Altekruse <
> altekruseja...@gmail.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > I'd like to propose the forth release candidate (rc3) of Apache Drill,
> > > version
> > > 1.5.0. It covers a total of 60 resolved JIRAs [1]. Thanks to everyone
> who
> > > contributed to this release. This release candidate includes fixes for
> > > DRILL-4235 and DRILL-4380, both regressions found sine the last release
> > > candidate.
> > >
> > > I also pulled in two bug fixes (4230, 4349) that had been merged into
> > > master since making the release branch, they looked useful to include
> and
> > > were both had little risk of introducing regressions.
> > >
> > > The tarball artifacts are hosted at [2] and the maven artifacts are
> > hosted
> > > at
> > > [3]. This release candidate is based on commit
> > > 3f228d34782741457a14e28b0d1fdbc35a4fd958 located at [4].
> > >
> > > The vote will be open for the next 72 hours ending at 7 PM Pacific,
> > > February 12th, 2016.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> > > Here's my vote: +1
> > >
> > > Thanks,
> > > Jason
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12332948
> > >
> > > [2] http://people.apache.org/~json/apache-drill-1.5.0.rc3/
> > > [3]
> > https://repository.apache.org/content/repositories/orgapachedrill-1028
> > > [4] https://github.com/jaltekruse/incubator-drill/tree/drill-1.5.0-rc3
> > >
> >
>

[GitHub] drill pull request: DRILL-4363: Row count based pruning for parque...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/drill/pull/371


---
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: DRILL-4363: Row count based pruning for parque...

[amansinha100]

Github user amansinha100 commented on the pull request:

https://github.com/apache/drill/pull/371#issuecomment-183125598
  
Updated patch looks good to me.  +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: DRILL-4383: Allow custom configurations to be ...

[jaltekruse]

GitHub user jaltekruse opened a pull request:

https://github.com/apache/drill/pull/375

DRILL-4383: Allow custom configurations to be specified for a FileSys…

…tem plugin

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaltekruse/incubator-drill 
4383-filesystem-conf

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/drill/pull/375.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 #375


commit 3bfc0d0905fa3eda27ce491914f666d595f46ddb
Author: Jason Altekruse 
Date:   2016-02-12T00:52:38Z

DRILL-4383: Allow custom configurations to be specified for a FileSystem 
plugin




---
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: [VOTE] Release Apache Drill 1.5.0 RC3

[rahul challapalli]

+1 (non-binding)

Built from source and ran the Functional and Advanced suites from the test
framework.
Performed some sanity tests against web ui authentication.

On Thu, Feb 11, 2016 at 4:03 PM, Jason Altekruse 
wrote:

> Thanks for the vote Sudheesh!
>
> Please, others with time available try out the candidate, the vote is
> supposed to close tomorrow at 7PM Pacific.
>
> Thanks,
> Jason
>
> On Thu, Feb 11, 2016 at 3:53 PM, Sudheesh Katkam 
> wrote:
>
> > +1 (non-binding; committer)
> >
> > * downloaded and built from source tar-ball; ran unit tests successfully
> on
> > Ubuntu
> > * ran simple queries (including cancellations) in embedded mode on Mac;
> > verified states in web UI
> > * ran simple queries (including cancellations) on a 3 node cluster;
> > verified states in web UI
> > * verified that queries complete with queuing enabled
> > * verified md5 and sha1 checksums on binary and src tar-balls, and zipped
> > folder
> >
> > Thank you,
> > Sudheesh
> >
> > On Tue, Feb 9, 2016 at 7:38 PM, Jason Altekruse <
> altekruseja...@gmail.com>
> > wrote:
> >
> > > For anyone who jumped on testing out the release candidate early I'm
> > going
> > > to have to ask you to re-download the artifacts you verified. I had
> > > prepared an earlier version of this candidate (but didn't get a chance
> to
> > > start the vote) before another regression was identified and fixed
> > today. I
> > > had forgotten to update the source and binary artifacts on my apache
> web
> > > space with the new ones.
> > >
> > > I just uploaded the corrected versions of the artifacts after verifying
> > > their git.properties files to ensure they were the correct versions.
> > >
> > > The last modified dates on the correct versions are between:
> 10-Feb-2016
> > > 03:30 and 10-Feb-2016 03:34
> > >
> > > (the copy took a few minutes as my home upload speed isn't great :P)
> > >
> > > Sorry about the mistake, everything should be good to go now.
> > >
> > > Thanks,
> > > Jason
> > >
> > >
> > >
> > > On Tue, Feb 9, 2016 at 7:08 PM, Jason Altekruse <
> > altekruseja...@gmail.com>
> > > wrote:
> > >
> > > > Hello all,
> > > >
> > > > I'd like to propose the forth release candidate (rc3) of Apache
> Drill,
> > > > version
> > > > 1.5.0. It covers a total of 60 resolved JIRAs [1]. Thanks to everyone
> > who
> > > > contributed to this release. This release candidate includes fixes
> for
> > > > DRILL-4235 and DRILL-4380, both regressions found sine the last
> release
> > > > candidate.
> > > >
> > > > I also pulled in two bug fixes (4230, 4349) that had been merged into
> > > > master since making the release branch, they looked useful to include
> > and
> > > > were both had little risk of introducing regressions.
> > > >
> > > > The tarball artifacts are hosted at [2] and the maven artifacts are
> > > hosted
> > > > at
> > > > [3]. This release candidate is based on commit
> > > > 3f228d34782741457a14e28b0d1fdbc35a4fd958 located at [4].
> > > >
> > > > The vote will be open for the next 72 hours ending at 7 PM Pacific,
> > > > February 12th, 2016.
> > > >
> > > > [ ] +1
> > > > [ ] +0
> > > > [ ] -1
> > > >
> > > > Here's my vote: +1
> > > >
> > > > Thanks,
> > > > Jason
> > > >
> > > > [1]
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12332948
> > > >
> > > > [2] http://people.apache.org/~json/apache-drill-1.5.0.rc3/
> > > > [3]
> > > https://repository.apache.org/content/repositories/orgapachedrill-1028
> > > > [4]
> https://github.com/jaltekruse/incubator-drill/tree/drill-1.5.0-rc3
> > > >
> > >
> >
>

[jira] [Created] (DRILL-4383) Allow passign custom configuration options to a file system through the storage plugin config

[Jason Altekruse (JIRA)]

Jason Altekruse created DRILL-4383:
--

 Summary: Allow passign custom configuration options to a file 
system through the storage plugin config
 Key: DRILL-4383
 URL: https://issues.apache.org/jira/browse/DRILL-4383
 Project: Apache Drill
  Issue Type: Improvement
  Components: Storage - Other
Reporter: Jason Altekruse
Assignee: Jason Altekruse
 Fix For: 1.6.0


A similar feature already exists in the Hive and Hbase plugins, it simply 
provides a key/value map for passing custom configuration options to the 
underlying storage system.

This would be useful for the filesystem plugin to configure S3 without needing 
to create a core-site.xml file or restart Drill.



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

[GitHub] drill pull request: DRILL-4383: Allow custom configurations to be ...

[jacques-n]

Github user jacques-n commented on the pull request:

https://github.com/apache/drill/pull/375#issuecomment-183136555
  
lgtm


---
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: Drill 4260: Adding support for "some" custom f...

[amansinha100]

Github user amansinha100 commented on a diff in the pull request:

https://github.com/apache/drill/pull/340#discussion_r52672160
  
--- Diff: 
exec/java-exec/src/test/java/org/apache/drill/exec/physical/impl/window/TestWindowFrame.java
 ---
@@ -106,6 +106,60 @@ public void testMultipleFramers() throws Exception {
 );
   }
 
+  @Test
+  public void testUnboundedFollowing() throws Exception {
+testBuilder()
+  .sqlQuery(getFile("window/q3.sql"), TEST_RES_PATH)
+  .ordered()
+  .sqlBaselineQuery(getFile("window/q4.sql"), TEST_RES_PATH)
+  .build()
+  .run();
+  }
+
+  @Test
+  public void testAggregateRowsUnboundedAndCurrentRow() throws Exception {
+final String table = "dfs_test.`"+TEST_RES_PATH+"/window/b4.p4`";
+testBuilder()
+  .sqlQuery(getFile("window/aggregate_rows_unbounded_current.sql"), 
table)
+  .ordered()
+  
.sqlBaselineQuery(getFile("window/aggregate_rows_unbounded_current_baseline.sql"),
 table)
+  .build()
+  .run();
+  }
+
+  @Test
+  public void testLastValueRowsUnboundedAndCurrentRow() throws Exception {
+final String table = "dfs_test.`"+TEST_RES_PATH+"/window/b4.p4`";
+testBuilder()
+  .sqlQuery(getFile("window/last_value_rows_unbounded_current.sql"), 
table)
+  .unOrdered()
+  
.sqlBaselineQuery(getFile("window/last_value_rows_unbounded_current_baseline.sql"),
 table)
+  .build()
+  .run();
+  }
+
+  @Test
+  public void testAggregateRangeCurrentAndCurrent() throws Exception {
--- End diff --

For the RANGE frame specification, are there unit tests that have the same 
ORDER-BY value repeating across multiple batches ?  This will form the peer 
group for the range...


---
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: [VOTE] Release Apache Drill 1.5.0 RC3

[Sudheesh Katkam]

+1 (non-binding; committer)

* downloaded and built from source tar-ball; ran unit tests successfully on
Ubuntu
* ran simple queries (including cancellations) in embedded mode on Mac;
verified states in web UI
* ran simple queries (including cancellations) on a 3 node cluster;
verified states in web UI
* verified that queries complete with queuing enabled
* verified md5 and sha1 checksums on binary and src tar-balls, and zipped
folder

Thank you,
Sudheesh

On Tue, Feb 9, 2016 at 7:38 PM, Jason Altekruse 
wrote:

> For anyone who jumped on testing out the release candidate early I'm going
> to have to ask you to re-download the artifacts you verified. I had
> prepared an earlier version of this candidate (but didn't get a chance to
> start the vote) before another regression was identified and fixed today. I
> had forgotten to update the source and binary artifacts on my apache web
> space with the new ones.
>
> I just uploaded the corrected versions of the artifacts after verifying
> their git.properties files to ensure they were the correct versions.
>
> The last modified dates on the correct versions are between: 10-Feb-2016
> 03:30 and 10-Feb-2016 03:34
>
> (the copy took a few minutes as my home upload speed isn't great :P)
>
> Sorry about the mistake, everything should be good to go now.
>
> Thanks,
> Jason
>
>
>
> On Tue, Feb 9, 2016 at 7:08 PM, Jason Altekruse 
> wrote:
>
> > Hello all,
> >
> > I'd like to propose the forth release candidate (rc3) of Apache Drill,
> > version
> > 1.5.0. It covers a total of 60 resolved JIRAs [1]. Thanks to everyone who
> > contributed to this release. This release candidate includes fixes for
> > DRILL-4235 and DRILL-4380, both regressions found sine the last release
> > candidate.
> >
> > I also pulled in two bug fixes (4230, 4349) that had been merged into
> > master since making the release branch, they looked useful to include and
> > were both had little risk of introducing regressions.
> >
> > The tarball artifacts are hosted at [2] and the maven artifacts are
> hosted
> > at
> > [3]. This release candidate is based on commit
> > 3f228d34782741457a14e28b0d1fdbc35a4fd958 located at [4].
> >
> > The vote will be open for the next 72 hours ending at 7 PM Pacific,
> > February 12th, 2016.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Here's my vote: +1
> >
> > Thanks,
> > Jason
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12332948
> >
> > [2] http://people.apache.org/~json/apache-drill-1.5.0.rc3/
> > [3]
> https://repository.apache.org/content/repositories/orgapachedrill-1028
> > [4] https://github.com/jaltekruse/incubator-drill/tree/drill-1.5.0-rc3
> >
>

[GitHub] drill pull request: Drill 4260: Adding support for "some" custom f...

[amansinha100]

Github user amansinha100 commented on the pull request:

https://github.com/apache/drill/pull/340#issuecomment-183070887
  
+1.  I gave a couple of comments; overall LGTM.


---
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.
---

expected behavior when using wild cards in table name

[Abdel Hakim Deneche]

I have the following table tpch100/lineitem that contains 97 parquet files:

tpch100/lineitem/part-m-0.parquet
tpch100/lineitem/part-m-1.parquet
tpch100/lineitem/part-m-2.parquet

...
tpch100/lineitem/part-m-00096.parquet

I can run the following queries:

SELECT COUNT(*) FROM `tpch100/lineit*;
SELECT COUNT(*) FROM `tpch100/lineitem/part-m-0001*';
SELECT COUNT(*) FROM `tpch100/lineitem/*';

The third query will fail if the table has metadata (it has to do with the
.drill.parquet_metadata showing up at the top of the file system results)

My question is: should the 2nd and 3rd queries be allowed, if we are
querying a table folder that doesn't contain any sub folders  ?

-- 

Abdelhakim Deneche

Software Engineer

  


Now Available - Free Hadoop On-Demand Training

Re: expected behavior when using wild cards in table name

[Steven Phillips]

I don't understand why they wouldn't be allowed. They seem perfectly valid.

On Thu, Feb 11, 2016 at 9:42 AM, Abdel Hakim Deneche 
wrote:

> I have the following table tpch100/lineitem that contains 97 parquet files:
>
> tpch100/lineitem/part-m-0.parquet
> tpch100/lineitem/part-m-1.parquet
> tpch100/lineitem/part-m-2.parquet
>
> ...
> tpch100/lineitem/part-m-00096.parquet
>
> I can run the following queries:
>
> SELECT COUNT(*) FROM `tpch100/lineit*;
> SELECT COUNT(*) FROM `tpch100/lineitem/part-m-0001*';
> SELECT COUNT(*) FROM `tpch100/lineitem/*';
>
> The third query will fail if the table has metadata (it has to do with the
> .drill.parquet_metadata showing up at the top of the file system results)
>
> My question is: should the 2nd and 3rd queries be allowed, if we are
> querying a table folder that doesn't contain any sub folders  ?
>
> --
>
> Abdelhakim Deneche
>
> Software Engineer
>
>   
>
>
> Now Available - Free Hadoop On-Demand Training
> <
> http://www.mapr.com/training?utm_source=Email_medium=Signature_campaign=Free%20available
> >
>

Re: expected behavior when using wild cards in table name

[Abdel Hakim Deneche]

I guess I was mainly thinking about parquet tables created by Drill, in
this case selecting a subset of the files wouldn't make sense, right ?

On Thu, Feb 11, 2016 at 10:32 AM, Steven Phillips  wrote:

> I don't understand why they wouldn't be allowed. They seem perfectly valid.
>
> On Thu, Feb 11, 2016 at 9:42 AM, Abdel Hakim Deneche <
> adene...@maprtech.com>
> wrote:
>
> > I have the following table tpch100/lineitem that contains 97 parquet
> files:
> >
> > tpch100/lineitem/part-m-0.parquet
> > tpch100/lineitem/part-m-1.parquet
> > tpch100/lineitem/part-m-2.parquet
> >
> > ...
> > tpch100/lineitem/part-m-00096.parquet
> >
> > I can run the following queries:
> >
> > SELECT COUNT(*) FROM `tpch100/lineit*;
> > SELECT COUNT(*) FROM `tpch100/lineitem/part-m-0001*';
> > SELECT COUNT(*) FROM `tpch100/lineitem/*';
> >
> > The third query will fail if the table has metadata (it has to do with
> the
> > .drill.parquet_metadata showing up at the top of the file system results)
> >
> > My question is: should the 2nd and 3rd queries be allowed, if we are
> > querying a table folder that doesn't contain any sub folders  ?
> >
> > --
> >
> > Abdelhakim Deneche
> >
> > Software Engineer
> >
> >   
> >
> >
> > Now Available - Free Hadoop On-Demand Training
> > <
> >
> http://www.mapr.com/training?utm_source=Email_medium=Signature_campaign=Free%20available
> > >
> >
>



-- 

Abdelhakim Deneche

Software Engineer

  


Now Available - Free Hadoop On-Demand Training