Re: Potential resource for large scale testing

; >> > They are otherwise just a regular machines, and run regular JVMs > on > > > >> Linux. > > > >> > > > > >> > We can also get Rahul an access with a secure token to setup > > > >> > and run stress/performan

Re: Timing for 1.2 release, ideas around things to include

iewable) off of this release. Any > > > thoughts on when everyone would like to do a release? Also, anyone want > > to > > > be release manager? > > > > > > Jacques > > > > > > -- > > > Jacques Nadeau > > > CTO and Co-Founde

Re: Timing for 1.2 release, ideas around things to include

the release. > > > > Great! I use a manual variation of these steps [1] typically. Julian Hyde > made a much nicer set of steps (for Incubator) here: [2] if you want to use > those. > > On Thu, Oct 1, 2015 at 2:32 PM, Parth Chandra wrote: > > > +1 on the release. I&#

Re: Timing for 1.2 release, ideas around things to include

e.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc > > > > -- > > Jacques Nadeau > > CTO and Co-Founder, Dremio > > > > On Thu, Oct 1, 2015 at 5:45 PM, Jacques Nadeau > wrote: > > > >> How about now? > >> > >> > >> &g

Re: Drill Hangout starting now

Join us here: > https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc >

Drill Hangout minutes - 2015-10-06 Re: Drill Hangout starting now

n the performance cluster. On Tue, Oct 6, 2015 at 10:06 AM, Parth Chandra wrote: > > > Join us here: >> https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc >> > >

Re: [VOTE] Release Apache Drill 1.2.0 RC2

+1. This one looks good. Downloaded source. Verified checksums Built from source. Built C++ client from source (MacOS) Tested multiple parallel queries via C++ client query submitter. All looks good. On Thu, Oct 8, 2015 at 2:08 PM, Abdel Hakim Deneche wrote: > Hi all, > > I'm enjoying the re

Drill Hangout starting now

Join us here: > https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc >

Re: Drill Hangout 20151013 Minutes

; > > Can we use this link today: > > > > > > https://plus.google.com/hangouts/_/dremio.com/drillhangout?authuser=0 > > > > > > -- > > > Jacques Nadeau > > > CTO and Co-Founder, Dremio > > > > > > On Tue, Oct 13, 2015 at 10:07 AM, Parth Chandra > > > > wrote: > > > > > > > Join us here: > > > > > > https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc > > > > > > > > > > > > > > >

Re: [VOTE] Release Apache Drill 1.2.0 RC3

Democracy is struggling to survive here. Please remember to vote today. On Mon, Oct 12, 2015 at 7:28 AM, Abdel Hakim Deneche wrote: > Hi all, > > I propose a fourth release candidate of Apache Drill 1.2.0 > > The tarball artifacts are hosted at [1] and the maven artifacts are hosted > at [2].

Re: [VOTE] Release Apache Drill 1.2.0 RC3

+1. Downloaded source. Verified checksums Built from source (MacOS) Built C++ client from source (MacOS) Tested multiple parallel queries (both sync and async APIs) via C++ client query submitter. Tested cancel from the c++client. Looks good. On Mon, Oct 12, 2015 at 7:28 AM, Abdel Hakim Denec

[DISCUSS] Design Documents

Hi guys, Now that 1.2 is out I wanted to bring up the exciting topic of design documents for Drill. As the project gets more contributors, we definitely need to start documenting our designs and also allow for a more substantial review process. In particular, we need to make sure that there is suf

Re: [DISCUSS] Design Documents

ing items. Contributors need > to perceive value in presenting a design doc. Let's get the WIIFM right so > that developer incentives are aligned. > > Jacques > > > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Fri, Oct 16, 2015 at 10:21 AM, Parth

Re: [DISCUSS] Design Documents

ocuments. So +1 long term but -1 until people start > to respond and provide feedback on the outstanding items. Contributors need > to perceive value in presenting a design doc. Let's get the WIIFM right so > that developer incentives are aligned. > > Jacques > > > > --

Re: [DISCUSS] Design Documents

writing the > > > design for features/mini features. It always seems to help in flushing > > out > > > both the internal and externally visible aspects of the feature. > Related > > > to this is the question 'what type of review or response to a review

Re: Drill 1.3 Timing: Let's start the vote next week

No problem with moving to the monthly cycle, but I thought that we were going to target the 12th of each month as the vote date. On Mon, Oct 26, 2015 at 11:40 AM, Jacques Nadeau wrote: > Hey Guys, > > We talked about moving to a start of month release cycle and we're > approaching a start of mon

Re: [DISCUSS] Proposal to turn ValueVectors into separate reusable library & project

+1. Agree with Hanifi that we probably should have done this sooner :). Jason and I faced this need when trying to get a stand alone vectorized parquet reader out of the Drill code last year. On Mon, Oct 26, 2015 at 2:37 PM, Hanifi Gunes wrote: > I was hoping to see this discussion happening s

Re: Drill 1.3 Timing: Let's start the vote next week

big concern. Sound okay? > > > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Mon, Oct 26, 2015 at 2:16 PM, Parth Chandra wrote: > > > No problem with moving to the monthly cycle, but I thought that we were > > going to target the 12th of each month as th

Re: [DISCUSS] Ideas to improve metadata cache read performance

And ideally, I suppose, the merged schema would correspond to the information that we want to keep in a .drill file. On Tue, Oct 27, 2015 at 4:55 PM, Aman Sinha wrote: > @Steven, w.r.t to your suggestion about doing the metadata operation during > execution phase, see the related discussion in

Re: Drill 1.3 Timing: Let's start the vote next week

; Jacques > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Mon, Oct 26, 2015 at 6:33 PM, Parth Chandra > wrote: > > > I remember that the we settled on sending out for vote on the 12th. > > > > Minutes from the hangout : > > > > > htt

Re: [DISCUSS] Ideas to improve metadata cache read performance

Hey Jacques, Steven, Do we have a branch somewhere which has the initial prototype code? I'd like to prune the file a bit as it looks like reducing the size of the metadata cache file might yield the best results. Also, did we have a particular reason for going with JSON as opposed to a more

Re: [DISCUSS] Ideas to improve metadata cache read performance

https://github.com/StevenMPhillips/drill/tree/meta > > On Fri, Oct 30, 2015 at 3:01 PM, Parth Chandra wrote: > > > Hey Jacques, Steven, > > > > Do we have a branch somewhere which has the initial prototype code? I'd > > like to prune the file a bit as it look

Re: Drill Hangout Happening

Hangout at the following link : https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc

Re: [DISCUSS] Ideas to improve metadata cache read performance

Unless we want to essentially disable value-based > > partition > > > > pruning when using the cache, the old code will not work. > > > > > > > > My recommendation would be to come up with a new version of the > format > > > > which sto

Re: [DISCUSS] Improving Fast Schema

I like the idea of making Parquet/Hive schema'd and returning the schema at planning time. Front end tools assume that the backend can do a Prepare and then Execute and this fits that model much better. On Thu, Nov 5, 2015 at 1:16 PM, Jacques Nadeau wrote: > The only way we get to a few millis

Re: [DISCUSS] Ideas to improve metadata cache read performance

n's parallelization comments are more applicable to > some of these than others. > > > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Wed, Nov 4, 2015 at 3:59 PM, Parth Chandra wrote: > > > It's been on my things to try. I'll give it a

Re: dot drill file

Hi Julien, In an earlier discussion, regarding 'insert into' we had discussed the idea of keeping a merged schema (a common schema that applies to all the files in the directory) in a .drill file. The metadata cache file also has the same information and, in addition, has stats. We never did s

Re: Nice piece I missed on Java profiling

Nice. Funny how this takes you back to the good old days of working with C. :) On Sat, Nov 7, 2015 at 5:34 PM, Jacques Nadeau wrote: > > http://www.brendangregg.com/blog/2015-11-06/java-mixed-mode-flame-graphs.html >

Re: Java graphical application being launched during the Drill build?

Yes I see it too. Just a minor annoyance I thought. On Mon, Nov 9, 2015 at 2:59 PM, Sudheesh Katkam wrote: > I did, on my Mac. However, I haven’t looked into it. > > > On Nov 9, 2015, at 2:57 PM, Jason Altekruse > wrote: > > > > Hello all, > > > > Has anyone else noticed a java graphical applic

Re: Drill tests on HPC

@Steven, @Jacques, Any suggestions and/or thoughts on Dechang's proposal. On Wed, Nov 18, 2015 at 11:53 AM, Dechang Gu wrote: > Hi All, > With the help and support from Edmon, I am going to leverage the > HPC resources at NICS ( https://www.nics.tennessee.edu/ < > https://www.nics.tennessee.ed

Re: Create 1.4 Release branch soon?

+1 on creating the release branch today. I'd like to get DRILL-4053 in. Patch is ready and doing one more round of regression tests. On Tue, Dec 1, 2015 at 9:56 AM, Jacques Nadeau wrote: > It is December (already!). Seems like we should create a 1.4 release branch > soon so we can get a vote g

Re: Can we pass the #skipped records with RecordBatch?

+1 on having a framework. OTOH, as with the warnings implementation, we might want to go ahead with a simpler implementation while we get a more generic framework design in place. Jacques, do you have any preliminary thoughts on the framework? On Tue, Dec 1, 2015 at 2:08 PM, Julian Hyde wrote:

Re: Parquet pushdown filtering

Parquet metadata has the rowCount for every rowGroup which is also the value count for every column in the rowGroup. Isn't that what you need? On Tue, Dec 1, 2015 at 10:10 PM, Adam Gilmore wrote: > Hi guys, > > I'm trying to (re)implement pushdown filtering for Parquet with the new > Parquet met

Re: [VOTE] Release Apache Drill 1.4.0 RC1

LGTM. +1 (binding) Downloaded src, validated checksums. Built from src tarball. Built C++ client. Tested multiple simultaneous simple queries using C++ query submitter using both sync/async APIs. Tested cancel. On Tue, Dec 8, 2015 at 7:54 AM, Venki Korukanti wrote: > Hi, > > I'd like to propo

Re: Parquet pushdown filtering

t; > > with > > > > > no > > > > > > schema. > > > > > > > > > > > > *- Scan batches don't allow empty batches. This means if a > > > > > > particular filter filters out *all* rows, we get an except

Re: Parquet pushdown filtering

> > > On Fri, Dec 11, 2015 at 11:42 AM, Parth Chandra > > wrote: > > > > > I'd like to attend as well. Any time that works for Julien/Jason works > > for > > > me. > > > > > > > > > > > > > > > >

Re: Can we pass the #skipped records with RecordBatch?

Some thoughts on the proposal and open issues (in no particular order)- The sideband mechanism allows any two points to pass data from one to another. This can be used to create arbitrary graphs of data flows which might not be desirable. To Juilan's point, maybe we need to set up the tunnels at D

Re: Naming the new ValueVector Initiative

On Tue, Jan 12, 2016 at 9:57 AM, Wes McKinney wrote: > > > > > As far as the existing work is concerned, I'm not sure everyone is aware > of > > the C++ code inside of Drill that can represent at least the scalar > types in > > Drill's existing Value Vectors [1]. This is currently used by the nat

Re: Client Load-balancing and Session Stickiness

With a client connection pool, there is no good (and easy) way to provide session stickiness. We could try to introduce the idea of a cluster wide session, but that is going to be hairy. Th other option, localizing it to a client is for the client to maintain session settings and setting them expl

Re: Hangout Happening Now!

Hey Jason, We're unable to connect to the hangout. Should we try restarting the hangout? Parth On Tue, Feb 23, 2016 at 10:04 AM, Jason Altekruse wrote: > https://plus.google.com/hangouts/_/dremio.com/drillhangout?authuser=1 >

Re: The praises for Drill

Welcome back Edmon, and thanks for the praise :). Hope to see you on the next hangout. On Thu, Feb 25, 2016 at 7:27 PM, Edmon Begoli wrote: > Hello fellow Driilers, > > I have been inactive on the development side of the project, as we got busy > being heavy/power users of the Drill in the last

Time for the 1.6 Release

Hello everyone, It's time to start looking into the 1.6 release. Can all the folks working on open issues let me know if there are any JIRAs you would like to get into the release? I know of the following - *DRILL-4281 *- Drill should support inbound impersonation. Pull request expected t

Re: Time for the 1.6 Release

t; to > > > > >> submit a snippet that will help with fixing it up (I think we just > > > need > > > > to > > > > >> do a look ahead byte lookup to ensure that it is not \r\n. > > > > >> > > > > >> On Tuesday, March 1, 2016, Jac

Re: Time for the 1.6 Release

gt; If this can get reviewed, I think it would be good to get into the release. > Any takers? > > On Wed, Mar 2, 2016 at 11:07 PM, Parth Chandra wrote: > > > I've summarized the list of JIRs below. > > The first set of pull requests is under review (or have some review

Re: Time for the 1.6 Release

Mar 3, 2016 at 6:30 PM, Parth Chandra wrote: > > > Here's an updated list with names of reviewers added. If anyone else is > > reviewing the open PRs please let me know. Some PRs have owners names > that > > I will follow up with. > > Jason, I've included

Re: Time for the 1.6 Release

r :). > > -- Zelaine > > On Thu, Mar 3, 2016 at 6:30 PM, Parth Chandra wrote: > > > Here's an updated list with names of reviewers added. If anyone else is > > reviewing the open PRs please let me know. Some PRs have owners names > that > > I will f

Re: Time for the 1.6 Release

r) (Owner: Hanifi) - Causes leak. Others - DRILL-2517 - Already resolved. DRILL-3688/pr 382 (skip.header.line.count in hive). - Already merged. PR needs to be closed. On Thu, Mar 3, 2016 at 9:44 PM, Parth Chandra wrote: > Right. My mistake. Thanks, Jacques, for reviewing. > > On Thu, M

Re: Heads up on trivial project fix: plan baselines in regression suite need updating

I'd be more comfortable if we merged this in after the release. Updating the test baselines will delay the release considerably - I would want the new baselines to be verified manually which is always time consuming. How many tests are affected? On Fri, Mar 4, 2016 at 10:03 AM, Jacques Nadeau w

Re: Time for the 1.6 Release

x27;ve > > > seen this plan instability in some of my recent test runs (even without > > > Java 8) when running extended HBase tests. > > > > > > -- > > > Jacques Nadeau > > > CTO and Co-Founder, Dremio > > > > > > On Thu,

Re: Time for the 1.6 Release

01 PM, Aditya wrote: > DRILL-4375/pr 402 - reviewed. > > On Sun, Mar 6, 2016 at 12:48 AM, Stefán Baxter > wrote: > > > Please review this and then consider as a potential blocker: > > > > https://issues.apache.org/jira/browse/DRILL-4482 > > > > > >

Re: Time for the 1.6 Release

> > > results issue, I already have a fix and it's passing all tests, I am > just > > > waiting for a review [2] > > > > > > > > > [1] https://issues.apache.org/jira/browse/DRILL-4457 > > > [2] https://github.com/apache/drill/pull/410 > > >

Re: Time for the 1.6 Release

ll have time, I would like to include DRILL-4457 [1], it's a > >> wrong > >>> results issue, I already have a fix and it's passing all tests, I am > just > >>> waiting for a review [2] > >>> > >>> > >>> [1] https://issu

Re: Time for the 1.6 Release

> > > > > > > On Mar 7, 2016, at 1:08 PM, Jacques Nadeau > > > wrote: > > > > > > > > > > > > The new bug (currently filed under DRILL-4384) is a completely > > > > different > > > > > &

Re: Time for the 1.6 Release

nd neither of the patches will have any impact on the > regression > > tests. One is a build fix, that only changes behavior when running the > > release profile and the other is a unit test fix. > > > > I had punted the operator unit tests out of the release, so those

Re: Time for the 1.6 Release

x27;m working on right now. > > - Jason > > On Tue, Mar 8, 2016 at 8:58 AM, Parth Chandra wrote: > > > Sounds good Jason. Let's finalize this in the hangout. > > Do you have the expected plans for the failing tests? If so can you > update > > those and put in

Re: Drill Hangout Today?

Joining in a minute On Tue, Mar 8, 2016 at 10:17 AM, Jason Altekruse wrote: > For anyone else interested in joining the hangout here is the link. > > https://plus.google.com/hangouts/_/dremio.com/drillhangout?authuser=1 > > On Tue, Mar 8, 2016 at 10:15 AM, Jason Altekruse > > wrote: > > > Yes,

Re: Time for the 1.6 Release

Hopefully there will be no show stoppers (. The plan is to roll out the release candidate by Thursday. Thanks Parth On Tue, Mar 8, 2016 at 9:31 AM, Parth Chandra wrote: > OK, let's leave it out then. > > On Tue, Mar 8, 2016 at 9:25 AM, Jason Altekruse > wrote: > >> To b

Re: Time for the 1.6 Release

Hi everyone, Just a note to update everyone that the QA team is testing out the build from master. There are no further commits expected for the 1.6.0 release. The repo is open for commits but try not to break anything :) Parth On Tue, Mar 8, 2016 at 5:16 PM, Parth Chandra wrote

Re: Time for the 1.6 Release

s still unresolved: > > https://issues.apache.org/jira/browse/DRILL-4120 > > > > It would mean a great deal to us if it was. > > The solution is, as I understood Jason and Jacques, ready and only needs > to > > be merged. > > > > Regards, > > -Stefá

Re: Time for the 1.6 Release

Hi guys, I've created the 1.6.0 branch and will be rolling out the first release candidate as soon as I get the go ahead from the QA team, in the next couple of hours. Thanks Parth On Thu, Mar 10, 2016 at 3:20 PM, Parth Chandra wrote: > It is usually not a good idea to try to r

Re: Time for the 1.6 Release

Done - Version in master branch updated to 1.7.0-SNAPSHOT On Thu, Mar 10, 2016 at 4:46 PM, Jacques Nadeau wrote: > You want to roll forward the current branch to 1.7.0-SNAPSHOT so we can > continue developing/merging stuff? > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > >

[VOTE] Release Apache Drill 1.6.0 - rc0

Hello all, I'd like to propose the zeroth release candidate (rc0) of Apache Drill, version 1.6.0. It covers a total of 44 resolved JIRAs [1]. Thanks to everyone who contributed to this release. The tarball artifacts are hosted at [2] and the maven artifacts are hosted at [3]. This release candid

Re: [VOTE] Release Apache Drill 1.6.0 - rc0

Amending for Daylight Savings Time The vote will be open for the next ~72 hours ending at *8*:10 AM PDT, March 14, 2016. Parth On Fri, Mar 11, 2016 at 7:09 AM, Parth Chandra wrote: > Hello all, > > I'd like to propose the zeroth release candidate (rc0) of Apache Drill, > ve

Re: [VOTE] Release Apache Drill 1.6.0 - rc0

ne in the past)? The link you have shows the > search results. > > thanks. > > On Fri, Mar 11, 2016 at 1:09 PM, Parth Chandra wrote: > > > Amending for Daylight Savings Time > > The vote will be open for the next ~72 hours ending at *8*:10 AM PDT, > March > > 14

Re: [VOTE] Release Apache Drill 1.6.0 - rc0

Added GPG key On Sat, Mar 12, 2016 at 6:48 PM, Aditya wrote: > I couldn't find your signing keys[1]. > > [1] https://github.com/apache/drill/blob/master/KEYS > > On Fri, Mar 11, 2016 at 7:09 AM, Parth Chandra wrote: > > > Hello all, > > > > I'd lik

Re: [VOTE] Release Apache Drill 1.6.0 - rc0

gt; > > wrote: > > > > > +1 > > > > > > built from source with mapr profile and deployed on 2 nodes, then run > > > window functions from Drill's test framework. Also took a quick look at > > the > > > WebUI. Everything looks fi

Re: [VOTE] Extended - Release Apache Drill 1.6.0 - rc0

4, 2016 at 8:12 AM, Parth Chandra wrote: > Aditya has verified the maven artifacts. Would it make sense to extend the > vote by another day to let more people verify the release? > > > > On Mon, Mar 14, 2016 at 7:08 AM, Jacques Nadeau > wrote: > >> I haven

[RESULT] [VOTE] Release Apache Drill 1.6.0 - rc0

508 > >> > >> <https://issues.apache.org/jira/browse/DRILL-4508> & DRILL-4509 > >> > >> <https://issues.apache.org/jira/browse/DRILL-4509>) > >> > >> > >> > >> Thanks > >> > >> Venki > >&g

Hangout Today?

Has the Hangout started? We are unable to connect.

[ANNOUNCE] Apache Drill 1.6.0 released

On behalf of *Apache* *Drill* community, I am happy to *announce* the release of *Apache* *Drill* 1.6.0. The source and binary artifacts are available at [1] Review a complete list of fixes and enhancements at [2] This release of *Drill* fixes many issues and introduces a number of enhancements,

[DRAFT REPORT] Apache Drill

It's time to file the Apache Drill quarterly report with the Board. Below is the draft of the report. Is there anything folks would like to add? Thanks Parth --- Report Begins ## Description: - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Sto

1.10 release

Hi Drill devs, Any thoughts on when we should do a 1.10 release? I can see a bunch of work (stats, managed sort, security) is in progress that is possibly fairly close to completion. Can the folks working on these items suggest a time frame that is comfortable for everyone? Parth

Re: [DRAFT REPORT] Apache Drill

I think we completed the dynamic UDFs feature before the previous report. It was mentioned in the report filed in November. On Fri, Feb 3, 2017 at 1:59 PM, Sudheesh Katkam wrote: > LGTM > > One more feature: ability to add UDFs dynamically > > > On Feb 3, 2017, at 10:47 AM, Pa

Re: [DRAFT REPORT] Apache Drill

Filing the following, updated with stats as of this morning. Report Begins ## Description: - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage ## Issues: - There are no issues requiring board attention at this time ## Activity: - Since the

[ANNOUNCE] New Apache Drill Committer - Abhishek Girish

The Project Management Committee (PMC) for Apache Drill has invited Abhishek Girish to become a committer and we are pleased to announce that he has accepted. Welcome Abhishek and thanks for your great contributions! Parth

[ANNOUNCE] NewApache Drill Committer - Rahul Challapalli

The Project Management Committee (PMC) for Apache Drill has invited Rahul Challapalli to become a committer and we are pleased to announce that he has accepted. Welcome Rahul and thanks for your great contributions! Parth

Re: [ANNOUNCE] New Committer: Arina Ielchiieva

Congratulations Arina. Welcome and thank you for your great work so far. On Fri, Feb 24, 2017 at 9:06 AM, Sudheesh Katkam wrote: > The Project Management Committee (PMC) for Apache Drill has invited Arina > Ielchiieva to become a committer, and we are pleased to announce that she > has accepte

Re: [VOTE] Release Apache Drill 1.10.0 - rc0

+1 (binding) Download and built from src. Verified signatures Ran a set of queries to test Parquet files. Ran some TPCH queries. Verified results. Looks good. On Sat, Mar 11, 2017 at 10:29 AM, Arina Yelchiyeva < arina.yelchiy...@gmail.com> wrote: > +1 > > - Downloaded tarball and started dri

Drill date & time types encoding

Paul asked this and I'm posting here so someone who knows better can correct me if I'm wrong ( This is from my notes when I was young) DATE : Int64 : Milliseconds from Unix Epoch : 1/1/1970 00:00:00 TIME : Int32 : Milliseconds from midnight on 1/1/1970 TimeStampTZ : Int64 + Int32 : (Milliseconds f

Re: Commissioning/Sponsoring Drill work :: Is it welcome?

Others may disagree, but I see no reason why you should not be allowed to approach contributors to work on specific items of interest to you. It is the reality that programmers have to pay bills too :). As long as any posts you make on the dev list are made with the goal of improvement to Drill I

Fwd: HuBot is deleting Apache project mirrors

: Fri, Apr 28, 2017 at 9:34 AM Subject: Re: HuBot is deleting Apache project morrors To: Parth Chandra Hi there, Sorry for the trouble! We've now had a couple of reports of this problem, and we've opened an issue internally to investigate. I don't have an ETA on a fix, but we&

DRAFT - ASF Board report for Apache Drill (May 2017)

Hi Drill devs, The quarterly report to the Apache Board is due again. Below is a draft of the report I plan to file. Any suggestions/additions from the dev team? I'll file this by the 3rd so please provide comments by then. Thanks Parth --- Report Begins --- ## Description: - Drill is a Schem

Re: Upgrading Netty

The per thread allocation cache in Netty causes unbounded memory growth in Drill because we pass the ownership of a buffer from one thread to another. The version we use has a fix for the Drill use case where Netty will no longer add a buffer to its per thread cache if the buffer was allocated by a

Re: [ANNOUNCE] New Committer: Paul Rogers

Congratulations Paul and thank you for your contributions to the project. Parth On Fri, May 19, 2017 at 9:20 AM, rahul challapalli < challapallira...@gmail.com> wrote: > Congratulations Paul. Well Deserved. > > On Fri, May 19, 2017 at 8:46 AM, Gautam Parai wrote: > > > Congratulations Paul and

Re: [ANNOUNCE] New Committer: Paul Rogers

I thinks it's time to put a link to Paul's wiki in the Apache Drill web site. On Fri, May 19, 2017 at 11:16 AM, Sudheesh Katkam wrote: > Forgot to mention, not many developers know about this: > https://github.com/paul-rogers/drill/wiki > > So thank you Paul, for that informative wiki, and all y

Re: Upgrading Netty

same thread for allocation and deallocation is noticable worse then before. We might want to do a performance run to make sure things are no worse than before. [1] https://github.com/netty/netty/commit/f765053ae740e300a6b696840d7dfe5de32afeb3 On Mon, May 15, 2017 at 5:46 PM, Parth Chandra

Re: Thinking about Drill 2.0

Nice suggestion Paul, to start a discussion on 2.0 (it's about time). I would like to make this a broader discussion than just APIs, though APIs are a good place to start. In particular. we usually get the opportunity to break backward compatibility only for a major release and that is the time we

Re: Thinking about Drill 2.0

Adding to my list of things to consider for Drill 2.0, I would think that getting Drill off our forks of Calcite and Parquet should also be a goal, though a tactical one. On Mon, Jun 5, 2017 at 1:51 PM, Parth Chandra wrote: > Nice suggestion Paul, to start a discussion on 2.0 (it'

[ANNOUNCE] New Committer: Laurent Goujon

The Project Management Committee (PMC) for Apache Drill has invited Laurent Goujon to become a committer, and we are pleased to announce that he has accepted. Laurent has a long list of contributions many in the client side interfaces and metadata queries. Welcome Laurent, and thank you for your

Re: Thinking about Drill 2.0

Some good work has been done in Arrow to get to a more formalized representation of complex types (lists and maps) particularly trying to address the nullability issues. My recommendation would be to get to a reasonable level of integration with Arrow and then start submitting changes/patches to Ar

Re: Native C++ Drill client handshake recovery

see inline responses On Thu, Jun 8, 2017 at 4:47 PM, Ralph Little wrote: > Hi, > I have been looking into an issue where the native client hangs after > failing to handshake during connection. > We have some boundary conditions where a connection is attempted while the > drill service is startin

[ANNOUNCE] New Committer: Charles Givre

The Project Management Committee (PMC) for Apache Drill has invited Charles Givre to become a committer, and we are pleased to announce that he has accepted. Charles was instrumental in taking the HTTPD format plugin to completion and since then has remained active on the user and dev list. He als

Re: Native C++ Drill client handshake recovery

Looks like the code should not be compiled out unless WIN32_SHUTDOWN_ON_TIMEOUT is defined. No reason for that to be defined on a non Windows platform. Query timeout is an artifact of the time when there was no heartbeat between Drill clients and the server, so it is possible there is some unexpec

Re: Native C++ Drill client handshake recovery

Hi Ralph, Sorry for the late response. For the commented out code, looks like it is wrong. I think we should check to see if m_pError is not null in all cases and return error if it is set to something. Regarding the other issue with a paused VM, I'm not sure what your VM setup is. Do you

Re: Re: Native C++ Drill client handshake recovery

Answers inline ... On Thu, Jun 22, 2017 at 1:43 PM, Ralph Little wrote: > Hi Parth, > Likewise, sorry for my tardy response: > >Sorry for the late response. >>For the commented out code, looks like it is wrong. I think we should >> check to see if m_pError is not null in all cases and re

Re: Timeline for the 1.11.0 release?

No we don't have a timeline, but per our policy, it is about time we did 1.11.0. I'll start a new thread. On Tue, Jun 20, 2017 at 3:35 PM, Abhishek Girish wrote: > Hey all, > > A couple of questions have come up on mailing lists and elsewhere asking > about the next release of Apache Drill. Do

[DISCUSS] Drill 1.11.0 release

Hello Drillers, It's been three months since the last release and it is time to do the next one. Does anyone want to volunteer to be the release manager? I would encourage our new committers to try their hand at it :) While we wait for volunteers, if there are any issues on which work is in p

[ANNOUNCE] New PMC Chair of Apache Drill

Hello Drill developers, I'm very pleased to announce that the Drill PMC has voted to elect Aman Sinha as the new PMC chair of Apache Drill. Please join me in congratulating Aman! Thanks, Parth

Re: [DISCUSS] Drill 1.11.0 release

th's handy scripts that > > should make the job lot easier. > > > > -Aman > > > > On Fri, Jun 23, 2017 at 4:45 AM, Arina Yelchiyeva < > > arina.yelchiy...@gmail.com> wrote: > > > > > If there are no objections, I'd like to volunteer.

Re: [DISCUSS] Drill 1.11.0 release

FWIW, I put release instructions culled from gists written by previous release managers into an updated gist here [1] HTH Parth [1] https://github.com/parthchandra/drill/wiki/Drill-Release-Process On Tue, Jun 27, 2017 at 5:24

  1   2   3   4   5   6   7   >