Re: Gradle?

Not particularly. Maven handles the needs so far pretty easily and has the considerable benefit of being bog standard. What benefit would you foresee with gradle? On Sat, Sep 12, 2015 at 9:02 PM, Edmon Begoli wrote: > Hey guys - has there been any consideration given to

Gradle?

Ted, I will tell you my opinion, not some deeply researched engineered position. Right now, I am looking into Gradle to be my primary build/release tool. I am not 100% set on it, but I see plenty of benefits, main being conciseness, configurabity, and robustness of the build process. In the

[GitHub] drill pull request: DRILL-1942-readers:

Github user amansinha100 commented on the pull request: https://github.com/apache/drill/pull/154#issuecomment-139897179 +1 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

Update on EDI support for Drill - repo and design collaboratory

Ted, Matt, et al., I have created temporary repository for design and development of the support for EDI format in Drill. At this point, it is not a fork of Drill, but rather a collaboration space and code repository for exploratory code. Wiki: https://github.com/ebegoli/edi-drill-store/wiki

[GitHub] drill pull request: DRILL-3735: For partition pruning divide up th...

GitHub user amansinha100 opened a pull request: https://github.com/apache/drill/pull/156 DRILL-3735: For partition pruning divide up the partition lists into … …sublists of 64K each and iterate over each sublist. Add abstract base class for various partition

[jira] [Created] (DRILL-3774) The Test TestExampleQueries.testTextPartitions fails consistently on fresh install

Jacques Nadeau created DRILL-3774: - Summary: The Test TestExampleQueries.testTextPartitions fails consistently on fresh install Key: DRILL-3774 URL: https://issues.apache.org/jira/browse/DRILL-3774

Re: Gradle?

I'm a huge Gradle fanatic and proponent, I use it for all of my projects large and small. However in this case I tend towards Ted's arguments. Maven is working well and it demands a little extra discipline that supports the ASF style. I expect and hope this changes in the future, but I've got

[jira] [Created] (DRILL-3773) Mongo RecordReader projection pushdown doesn't work past first level paths

Jacques Nadeau created DRILL-3773: - Summary: Mongo RecordReader projection pushdown doesn't work past first level paths Key: DRILL-3773 URL: https://issues.apache.org/jira/browse/DRILL-3773 Project:

Re: Gradle?

In that case ;) Gradle is faster, more attuned to incremental builds, has a daemon to remove startup time, and as of 2.6 has continuous builds so you don't even have to kick it off after you make changes to source :) Of course, with great power comes great responsibility. As an embedded DSL vs

Re: Update on EDI support for Drill - repo and design collaboratory

I doubt that I will be able to produce significant amounts of code. If I do produce much of anything, I would be happy to contribute via pull requests. So I don't need to be on the repo as a contributor. On Sun, Sep 13, 2015 at 1:42 PM, Edmon Begoli wrote: > Ted, Matt, et

Re: Gradle?

OK. To explain some of the reasons that moving has little force, here are some answers in-line. The summary is that I think that you are claiming that gradle offers a combination of readability, expressiveness and flexibility. My thought in response is that the readability difference is probably

Re: Gradle?

On Sun, Sep 13, 2015 at 3:43 PM, Matt Burgess wrote: > but I've got to go with the "not yet" Regardless of the decision, the discussion is still useful. These things have a habit of changing over time. I know that I have gone through quite a number of build systems in my

[jira] [Created] (DRILL-3775) Fix issues with TestMongoProjectPushDown

Jacques Nadeau created DRILL-3775: - Summary: Fix issues with TestMongoProjectPushDown Key: DRILL-3775 URL: https://issues.apache.org/jira/browse/DRILL-3775 Project: Apache Drill Issue Type:

[jira] [Resolved] (DRILL-3160) Make JDBC Javadoc documentation available to users

[ https://issues.apache.org/jira/browse/DRILL-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3160. --- Resolution: Fixed Merged in e43155d > Make JDBC Javadoc documentation available to users >

[jira] [Resolved] (DRILL-3458) Avro file format's support for map and nullable union data types.

[ https://issues.apache.org/jira/browse/DRILL-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3458. --- Resolution: Fixed Merged in fe07b6c > Avro file format's support for map and nullable union

[jira] [Resolved] (DRILL-3720) Avro Record Reader should process Avro files by per block basis

[ https://issues.apache.org/jira/browse/DRILL-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3720. --- Resolution: Fixed Merged in 8f4ca6e > Avro Record Reader should process Avro files by per

[jira] [Resolved] (DRILL-3589) JDBC driver maven artifact includes a lot of unnecessary dependencies

[ https://issues.apache.org/jira/browse/DRILL-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3589. --- Resolution: Fixed Resolved in 4e3b7dc > JDBC driver maven artifact includes a lot of

Re: Update on EDI support for Drill - repo and design collaboratory

I understand. I hope you and the rest will help me with design guidance as I start translating EDI format into a Drill-amenable one. On Sunday, September 13, 2015, Ted Dunning wrote: > I doubt that I will be able to produce significant amounts of code. If I do > produce

[GitHub] drill pull request: Drill 3180: Implement JDBC Storage Plugin

Github user asfgit closed the pull request at: https://github.com/apache/drill/pull/115 --- 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

[jira] [Resolved] (DRILL-3773) Mongo RecordReader projection pushdown doesn't work past first level paths

[ https://issues.apache.org/jira/browse/DRILL-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3773. --- Resolution: Fixed Merged in 97615e5 > Mongo RecordReader projection pushdown doesn't work

[jira] [Resolved] (DRILL-1666) Provide Test cases for Mongo Storage plugin

[ https://issues.apache.org/jira/browse/DRILL-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-1666. --- Resolution: Fixed Merged in 197d972 > Provide Test cases for Mongo Storage plugin >

[jira] [Resolved] (DRILL-3180) Apache Drill JDBC storage plugin to query rdbms systems such as MySQL and Netezza from Apache Drill

[ https://issues.apache.org/jira/browse/DRILL-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3180. --- Resolution: Fixed Fix Version/s: (was: 1.3.0) 1.2.0 Merged in

Drill- Query execution plan

Hi, Need some help understanding the below steps of a query execution. The below query is broken down in to these steps. If you could just explain me in short or point to a documentation link would be great for me as I am trying to dig into drill code and logics. SELECT SUM(1) AS `COL` FROM

[GitHub] drill pull request: DRILL-3724 - added javadoc for core classes fo...

Github user jacques-n commented on the pull request: https://github.com/apache/drill/pull/139#issuecomment-139965734 This has been merged. However, I forgot to include the "merged in" message so @ebegoli , can you please close? --- If your project is set up for it, you can reply to