[GitHub] drill pull request #850: DRILL-5541: C++ Client Crashes During Simple "Man i...

GitHub user superbstreak opened a pull request: https://github.com/apache/drill/pull/850 DRILL-5541: C++ Client Crashes During Simple "Man in the Middle" Atta… …ck Test with Exploitable Write AV You can merge this pull request into a Git repository by running: $ git pull

[jira] [Resolved] (DRILL-5567) Review changes for DRILL 5514

[ https://issues.apache.org/jira/browse/DRILL-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthikeyan Manivannan resolved DRILL-5567. --- Resolution: Done > Review changes for DRILL 5514 >

[GitHub] drill pull request #849: DRILL-5568: Include hadoop-common jars inside drill...

GitHub user sohami opened a pull request: https://github.com/apache/drill/pull/849 DRILL-5568: Include hadoop-common jars inside drill-jdbc-all.jar More details on this PR is in [JIRA](https://issues.apache.org/jira/browse/DRILL-5568) You can merge this pull request into a Git

[GitHub] drill pull request #837: DRILL-5514: Enhance VectorContainer to merge two ro...

Github user bitblender commented on a diff in the pull request: https://github.com/apache/drill/pull/837#discussion_r120198724 --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/record/BatchSchema.java --- @@ -157,4 +158,26 @@ private boolean majorTypeEqual(MajorType t1,

[GitHub] drill pull request #837: DRILL-5514: Enhance VectorContainer to merge two ro...

Github user bitblender commented on a diff in the pull request: https://github.com/apache/drill/pull/837#discussion_r118797793 --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/record/BatchSchema.java --- @@ -157,4 +158,26 @@ private boolean majorTypeEqual(MajorType t1,

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

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

[jira] [Created] (DRILL-5568) Include Hadoop dependency jars inside drill-jdbc-all.jar

Sorabh Hamirwasia created DRILL-5568: Summary: Include Hadoop dependency jars inside drill-jdbc-all.jar Key: DRILL-5568 URL: https://issues.apache.org/jira/browse/DRILL-5568 Project: Apache Drill

[jira] [Created] (DRILL-5567) Review changes for DRILL 5514

Karthikeyan Manivannan created DRILL-5567: - Summary: Review changes for DRILL 5514 Key: DRILL-5567 URL: https://issues.apache.org/jira/browse/DRILL-5567 Project: Apache Drill Issue

protobuf version

Hi List, I see that Apache Drill is limited to 2.x series for protobuf. I cannot find any reference as to why this is. Could someone explain the dependency restriction? Did something major change in the 3.x release series for protobuf? The only reason I ask is that protobuf 3.3 builds much

[jira] [Created] (DRILL-5566) AssertionError: Internal error: invariant violated: call to wrong operator

Khurram Faraaz created DRILL-5566: - Summary: AssertionError: Internal error: invariant violated: call to wrong operator Key: DRILL-5566 URL: https://issues.apache.org/jira/browse/DRILL-5566 Project:

[jira] [Created] (DRILL-5565) Directory Query fails with Permission denied: access=EXECUTE if dirN name is 'year=2017' or 'month=201704'

ehur created DRILL-5565: --- Summary: Directory Query fails with Permission denied: access=EXECUTE if dirN name is 'year=2017' or 'month=201704' Key: DRILL-5565 URL: https://issues.apache.org/jira/browse/DRILL-5565

Thinking about Drill 2.0

Hi All, A while back there was a discussion about the scope of Drill 2.0. Got me thinking about possible topics. My two cents: Drill 2.0 should focus on making Drill’s external APIs production ready. This means five things: * Clearly identify and define each API. * (Re)design each API to

[jira] [Created] (DRILL-5564) IllegalStateException: allocator[op:21:1:5:HashJoinPOP]: buffer space (16674816) + prealloc space (0) + child space (0) != allocated (16740352)

Khurram Faraaz created DRILL-5564: - Summary: IllegalStateException: allocator[op:21:1:5:HashJoinPOP]: buffer space (16674816) + prealloc space (0) + child space (0) != allocated (16740352) Key: DRILL-5564 URL:

[jira] [Created] (DRILL-5563) Stop non foreman Drillbit results in IllegalStateException: Allocator[ROOT] closed with outstanding child allocators.

Khurram Faraaz created DRILL-5563: - Summary: Stop non foreman Drillbit results in IllegalStateException: Allocator[ROOT] closed with outstanding child allocators. Key: DRILL-5563 URL: