[jira] [Created] (DRILL-3893) Issue with Drill after Hive Alters the Table

arnab chatterjee created DRILL-3893: --- Summary: Issue with Drill after Hive Alters the Table Key: DRILL-3893 URL: https://issues.apache.org/jira/browse/DRILL-3893 Project: Apache Drill Issu

Re: ensureAtLeastOneField: obsolete? needed?

On Sun, Oct 4, 2015 at 8:56 PM, Daniel Barclay wrote: > In what sense is that not supported? For example, where would returning > zero columns be expected to break? > The system wasn't designed with this in mind. That is why the iterator validator ensures that this isn't happening. If you want

Using PathFilter for directory pruning

Drill should try to prune directories 'as early as possible'; ideally at the time of reading from the filesystem the first time during planning phase. Could we take advantage of o.a.hadoop.fs.PathFilter to only read directories that match a pattern ? Currently, Drill uses PathFilter to skip certa

[jira] [Created] (DRILL-3894) Directory functions (MaxDir, MinDir ..) should have optional filename parameter

Neeraja created DRILL-3894: -- Summary: Directory functions (MaxDir, MinDir ..) should have optional filename parameter Key: DRILL-3894 URL: https://issues.apache.org/jira/browse/DRILL-3894 Project: Apache Dri

Re: Partial aggregation in Drill-on-Phoenix

Right now this type of work is done here: https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/planner/physical/HashAggPrule.java https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/planner/physical/AggPruleBase.j

[GitHub] drill pull request: DRILL-3845: Partition sender shouldn't send th...

Github user adeneche commented on the pull request: https://github.com/apache/drill/pull/173#issuecomment-145599844 @vkorukanti can you please review ? thx --- 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 d

Re: Partial aggregation in Drill-on-Phoenix

I actually tried implementing partial sort with https://github.com/jacques-n/drill/pull/4, which I figured might be a little easier to start with than partial aggregation. But I found that even though the code worked (returned the right results), the Drill side sort turned out to be a ordinary sort

[jira] [Created] (DRILL-3895) Can not join on int96 column coming from two different sources: hive and impala

Victoria Markman created DRILL-3895: --- Summary: Can not join on int96 column coming from two different sources: hive and impala Key: DRILL-3895 URL: https://issues.apache.org/jira/browse/DRILL-3895 P

[VOTE] Release Apache Drill 1.2.0 (rc0)

Hey all, I'm happy to propose a new release of Apache Drill, version 1.2.0. This is the first release candidate (rc0). Thanks to everyone who contributed to this release, we have more than 200 closed and resolved JIRAs [1]. The tarball artifacts are hosted at [2] and the maven artifacts (new for

Re: Partial aggregation in Drill-on-Phoenix

Maryann, I believe Jacques mentioned that a little bit of refactoring is required for a merge sort to occur - there's something that does that, but it's not expected to be used in this context currently. IMHO, there's more of a clear value in getting the aggregation to use Phoenix first, so I'd re

[GitHub] drill pull request: DRILL-3874: flattening large JSON objects uses...

Github user cwestin commented on the pull request: https://github.com/apache/drill/pull/181#issuecomment-145645022 This was merged. --- 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 featur

[GitHub] drill pull request: DRILL-3874: flattening large JSON objects uses...

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

Re: [VOTE] Release Apache Drill 1.2.0 (rc0)

One precision, the commit that should show up in the release is the following: b418397790e7e00505846d48bc6458d710c00095 upgrading maven-release plugin to fix release issues master has already moved past that commit thanks On Mon, Oct 5, 2015 at 11:00 AM, Abdel Hakim Deneche wrote: > Hey all,

Re: [VOTE] Release Apache Drill 1.2.0 (rc0)

I see the following in the release notes: this is not supported yet. Are you using the correct 'status' condition in your query ? - [DRILL-3534 ] - Insert into table support On Mon, Oct 5, 2015 at 1:16 PM, Abdel Hakim Deneche wrote: > O

RE: [VOTE] Release Apache Drill 1.2.0 (rc0)

+1 non-binding. Built from source and tested it with the ODBC driver. Executed simple queries against Hive, and various file formats in HDFS. Norris -Original Message- From: Abdel Hakim Deneche [mailto:adene...@maprtech.com] Sent: Monday, October 05, 2015 1:17 PM To: dev@drill.apache.o

Re: [VOTE] Release Apache Drill 1.2.0 (rc0)

Aman, I used JIRA release notes generator. It includes all JIRAs marked "Fix for" 1.2.0. I guess we just need to move all JIRAs still open and marked as 1.2.0 to 1.3.0 or Future. On Mon, Oct 5, 2015 at 1:54 PM, Aman Sinha wrote: > I see the following in the release notes: this is not supported

[jira] [Created] (DRILL-3896) Allow for dynamic allocation of resources during execution of concurrent queries

Kunal Khatua created DRILL-3896: --- Summary: Allow for dynamic allocation of resources during execution of concurrent queries Key: DRILL-3896 URL: https://issues.apache.org/jira/browse/DRILL-3896 Project:

How do I add projection capabilities to an operator that doesn't have them?

In particular, I'm trying to work on https://issues.apache.org/jira/browse/DRILL-3876 in order to reduce the amount of memory downstream operators require. I started looking at Projector.java and ProjectorTemplate.java, but it seems like copying that pattern wouldn't be enough -- how do I get the

Re: New Slack setup for Devs and Users

Is Slack threaded as e-mail is? (If not, and you can't see messages grouped by subject (that is, if it's the case that you can't see the tree of messages for a subject without wading through irrelevant messages that occurred at intervening times), how is Slack better than using the existing e-

Re: New Slack setup for Devs and Users

Slack is real time and handles multiple access points really seamlessly. Thus, I get a ding on my phone only if I am not logged in on my laptop. It scours discussions for keywords so that I can ignore things mostly and yet still pop in when the topics turn to what I need to be involved in. Email i

[jira] [Resolved] (DRILL-3895) Can not join on int96 column coming from two different sources: hive and impala

[ https://issues.apache.org/jira/browse/DRILL-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victoria Markman resolved DRILL-3895. - Resolution: Invalid > Can not join on int96 column coming from two different sources: hive

Re: ensureAtLeastOneField: obsolete? needed?

Jacques, > ... it ... should probably check if a column is already setup in the output mutation and, if so, don't re-add the ensure at least one column. Thus probably requires a new method in output mutator (isEmpty or size) Some questions on the various moving pieces: Does ensureAtLeastOneF

Re: New Slack setup for Devs and Users

+1 Sent from my iPhone > On Oct 5, 2015, at 6:15 PM, Ted Dunning wrote: > > Slack is real time and handles multiple access points really seamlessly. > Thus, I get a ding on my phone only if I am not logged in on my laptop. It > scours discussions for keywords so that I can ignore things mostly