Re: Hangout starting at 10am

Note, per the first item above, I've put together an initial proposal of the compatibility commitments we should make to the users. It is important to note that my outline is about our public commitment. As a development community, we should always work to avoid disruptive or backwards incompatible

Re: Proposal: Create v2 branch to work on breaking changes

A general policy shouldn't hold up a specific decision. Even after we establish a guiding policy, there will be exceptions that we will consider. I'm looking for concrete counterpoint to the cost of maintaining backwards compatibility. That being said, I have put together an initial proposal of th

Re: Proposal: Create v2 branch to work on breaking changes

Makes sense to postpone the debate : ) Will Look forward for the proposal. On Tuesday, April 12, 2016, Zelaine Fong wrote: > As we discussed at this morning's hangout, Jacques took the action to put > together a strawman compatibility points document. Would it be better to > wait for that docum

[jira] [Created] (DRILL-4600) Document Public Compatibility Comittments

Jacques Nadeau created DRILL-4600: - Summary: Document Public Compatibility Comittments Key: DRILL-4600 URL: https://issues.apache.org/jira/browse/DRILL-4600 Project: Apache Drill Issue Type:

[GitHub] drill pull request: DRILL-4589: Reduce planning time for file syst...

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

Re: Proposal: Create v2 branch to work on breaking changes

As we discussed at this morning's hangout, Jacques took the action to put together a strawman compatibility points document. Would it be better to wait for that document before we debate this further? -- Zelaine On Tue, Apr 12, 2016 at 4:39 PM, Jacques Nadeau wrote: > I agree with Paul, too. P

Re: Proposal: Create v2 branch to work on breaking changes

I agree with Paul, too. Perfect compatibility would be great. I recognize the issues that a version break could cause. These are some of the issues that I believe require a version break to address: - Support nulls in lists. - Distinguish null maps from empty maps. - Distinguish null arrays from e

[jira] [Resolved] (DRILL-4563) Add HOCON reference to Drill docs

[ https://issues.apache.org/jira/browse/DRILL-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bridget Bevens resolved DRILL-4563. --- Resolution: Fixed Updated the page based on comments in this ticket. > Add HOCON reference t

Re: Proposal: Create v2 branch to work on breaking changes

I agree with Paul. Great points. I would also add the partners aspect to it. Majority of Drill users use it in conjunction with a BI tool. -Neeraja On Tue, Apr 12, 2016 at 3:34 PM, Paul Rogers wrote: > Hi Jacques, > > My two cents… > > The unfortunate reality is that enterprise customers move

Re: Contributing to Drill?

Can a committer respond to this request? thanks, Jacques -- Jacques Nadeau CTO and Co-Founder, Dremio On Thu, Apr 7, 2016 at 9:07 AM, Zelaine Fong wrote: > A Drill user is eager to contribute a new XML plugin, and was planning to > follow the instructions noted at > https://drill.apache.org/do

Re: Proposal: Create v2 branch to work on breaking changes

Hi Jacques, My two cents… The unfortunate reality is that enterprise customers move slowly. There is a delay in the time it takes for end users to upgrade to a new release. When a third-party tool must also upgrade, the delay becomes even longer. At a high level, we need to provide a window of

Re: Proposal: Create v2 branch to work on breaking changes

>>What I am suggesting is that we need to maintain backward compatibility with a defined set of 1.x version clients when Drill 2.0 version is out. I'm asking you to be concrete on why. There is definitely a cost to maintaining this compatibility. What are the real costs if we don't? -- Jacques Na

[jira] [Resolved] (DRILL-3612) Doc. says logging configuration at /conf/logback.xml

[ https://issues.apache.org/jira/browse/DRILL-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bridget Bevens resolved DRILL-3612. --- Resolution: Fixed Missing back ticks around file path so the full path wasn't displaying on th

[jira] [Resolved] (DRILL-4440) Host file location for Windows incorrect in doc

[ https://issues.apache.org/jira/browse/DRILL-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bridget Bevens resolved DRILL-4440. --- Resolution: Fixed changed host file path > Host file location for Windows incorrect in doc >

[GitHub] drill pull request: DRILL-4527: remove DrillAvgVarianceConvertlet

Github user vkorukanti commented on the pull request: https://github.com/apache/drill/pull/441#issuecomment-209095889 LGTM, +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 ena

[GitHub] drill pull request: DRILL-4446: Support mandatory work assignment ...

Github user vkorukanti commented on the pull request: https://github.com/apache/drill/pull/403#issuecomment-209094651 Updated patch, Addressed review comments and also added couple of negative tests. --- If your project is set up for it, you can reply to this email and have y

Proposal to add site & node config

Hi All, As part of the Drill-on-YARN project we would like to split out user (“site”) configuration from that for Drill itself. We also want to split distribution-provided settings (such as those set by MapR) from user configuration. Finally, we want to separate per-node configuration from sit

[GitHub] drill pull request: DRILL-3714: Avoid cascading disconnection when...

Github user jacques-n commented on a diff in the pull request: https://github.com/apache/drill/pull/463#discussion_r59445000 --- Diff: exec/rpc/src/main/java/org/apache/drill/exec/rpc/RequestIdMap.java --- @@ -84,7 +115,7 @@ public void operationComplete(ChannelFuture future) thro

[GitHub] drill pull request: DRILL-4596: Drill should do version check amon...

Github user jacques-n commented on the pull request: https://github.com/apache/drill/pull/474#issuecomment-209081311 In general, I'm against version number checking. We did that in the code early on but we should be moving towards a capabilities flag approach. Also agree with

[GitHub] drill pull request: DRILL-3714: Avoid cascading disconnection when...

Github user jacques-n commented on a diff in the pull request: https://github.com/apache/drill/pull/463#discussion_r59434232 --- Diff: exec/rpc/src/main/java/org/apache/drill/exec/rpc/RequestIdMap.java --- @@ -20,51 +20,82 @@ import io.netty.buffer.ByteBuf; import io.nett

[GitHub] drill pull request: DRILL-3714: Avoid cascading disconnection when...

Github user jacques-n commented on a diff in the pull request: https://github.com/apache/drill/pull/463#discussion_r59433373 --- Diff: exec/rpc/src/main/java/org/apache/drill/exec/rpc/RequestIdMap.java --- @@ -20,51 +20,82 @@ import io.netty.buffer.ByteBuf; import io.nett

[GitHub] drill pull request: DRILL-3714: Avoid cascading disconnection when...

Github user jacques-n commented on a diff in the pull request: https://github.com/apache/drill/pull/463#discussion_r59433244 --- Diff: exec/rpc/src/main/java/org/apache/drill/exec/rpc/RequestIdMap.java --- @@ -20,51 +20,82 @@ import io.netty.buffer.ByteBuf; import io.nett

[jira] [Created] (DRILL-4599) Create Querying Avro Files content

Bridget Bevens created DRILL-4599: - Summary: Create Querying Avro Files content Key: DRILL-4599 URL: https://issues.apache.org/jira/browse/DRILL-4599 Project: Apache Drill Issue Type: Task

[jira] [Resolved] (DRILL-4598) Update Website to Mark Avro Support as Experimental

[ https://issues.apache.org/jira/browse/DRILL-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bridget Bevens resolved DRILL-4598. --- Resolution: Fixed Updated Avro as requested on http://drill.apache.org/docs/querying-a-file-s

Re: NPE running a CTAS query with Partition BY

The stack trace shows NPE was thrown by the Project operator before ParquetWriter operator. Can you go to WebUi and find that failed CTAS statement. In PhysicalPlan tab, copy and past the CTAS's plan here. It will give us some idea what that Project is doing. On Tue, Apr 12, 2016 at 8:49 AM, Al

Re: Hangout starting at 10am

Notes: Attendees: Paul, Parth, Zelaine, Jacques, Arrina, Vittali, Aman Main topics of discussion: Backwards compatibility. Everybody thinks that striving for backwards compatibility is good. However, we need to be formal about our goals as well as real costs to maintain. Jacques to put together

Hangout starting at 10am

https://plus.google.com/hangouts/_/dremio.com/drillhangout?authuser=0 -- Jacques Nadeau CTO and Co-Founder, Dremio

NPE running a CTAS query with Partition BY

Hi, I'm experiencing NPE running a CTAS query with Partition BY. Data in the SELECT statement comes from Hive (through Hive storage plugin). Any pointers? Thanks, Alex -- Alex Rodrigues, Data Engineer EMEA Mobile: +447449713454 | Skype: deorus Now Available - Free Hadoop

[GitHub] drill pull request: DRILL-4596: Drill should do version check amon...

Github user paul-rogers commented on the pull request: https://github.com/apache/drill/pull/474#issuecomment-208959253 Some other design issues. The idea of a rollling upgrade presupposes that we can shut down a Drillbit, bring up a new one, and the cluster keeps running. But, today,

[GitHub] drill pull request: DRILL-4596: Drill should do version check amon...

Github user paul-rogers commented on the pull request: https://github.com/apache/drill/pull/474#issuecomment-208943460 Hi All. Version compatibility is a complex issue. Do we have a design document that explains our goals and policy? Is the goal to allow rolling updates of clients? (D

[GitHub] drill pull request: DRILL-4596: Drill should do version check amon...

Github user arina-ielchiieva commented on a diff in the pull request: https://github.com/apache/drill/pull/474#discussion_r59332891 --- Diff: common/src/main/java/org/apache/drill/common/util/DrillVersionInfo.java --- @@ -49,10 +53,52 @@ public static String getVersion() {