[ANNOUNCE] Apache Drill 1.19.0 Released

On behalf of the Apache Drill community, I am happy to announce the release of Apache Drill 1.19.0. Drill is an Apache open-source SQL query engine for Big Data exploration. Drill is designed from the ground up to support high-performance analysis on the semi-structured and rapidly evolving data

[RESULT] [VOTE] Release Apache Drill 1.19.0 RC1

Hi all, The vote passes. Thanks to everyone who has tested the release candidate and given their comments and votes. Final tally: 3x +1 (binding): Laurent, Ted, Vova No 0s or -1s. I'll start the process for pushing the release artifacts and send an announcement once propagated. Kind regards,

[VOTE] Release Apache Drill 1.19.0 - RC1

Hi all, I'd like to propose the first release candidate (RC1) of Apache Drill, version 1.19.0. The release candidate covers a total of 109 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].

Re: [VOTE] Release Apache Drill 1.19.0 - RC0

bhakar Bhosaale wrote: > Vote +1 > > On Wed, Jun 2, 2021 at 3:12 AM Laurent Goujon wrote: > > > Hi all, > > > > I'd like to propose the first release candidate (RC0) of Apache Drill, > > version 1.19.0. > > The release candidate covers a total of 10

[VOTE] Release Apache Drill 1.19.0 - RC0

Hi all, I'd like to propose the first release candidate (RC0) of Apache Drill, version 1.19.0. The release candidate covers a total of 105 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].

Re: Enable debugging for 3rd party storage plugin with eclipse

It is more of a question for the Eclipse community I guess (I don't believe there are specific steps needed for Drill). I would also recommend checking Eclipse documentation:

Re: Apache Drill Hangout Minutes - 11/1/16

> difference is that the C++ client (unlike the Java client) checks for > the > > > server version as well, which make the compatibility break more > visible. > > > > > > I am not sure about the plan of action in general about this > > compatibility. > > &

Re: Apache Drill Hangout Minutes - 11/1/16

re visible. > > I am not sure about the plan of action in general about this compatibility. > However, I could work around the issue by advertising clients' SASL > capability to the server. What do you think? > > Thank you, > Sudheesh > > [1] https://issues.apache.org/jira/bro

Re: Apache Drill Hangout Minutes - 11/1/16

Just for clarity, DRILL-4280 is a breaking-protocol change, so is the plan to defer this change to a later release, or to defer bringing back compatibility between newer clients and older servers to a later release? Laurent On Tue, Nov 1, 2016 at 3:43 PM, Zelaine Fong wrote:

Re: Class not found exception

First, can you tell more about how you get the driver in the first place? If you got it from the distribution (following instructions at http://drill.apache.org/docs/using-jdbc/#step-1:-getting-the-drill-jdbc-driver), you should be good to go. If you try to build it from source, make sure you're

Re: [HANGOUT] Topics for 10/04/16

Hi, I'm currently working on improving metadata support for both the JDBC driver and the C++ connector, more specifically the following JIRAs: DRILL-4853: Update C++ protobuf source files DRILL-4420: Server-side metadata and prepared-statement support for C++ connector DRILL-4880: Support JDBC