Re: Time for a 1.1 vote soon?

I just had a clean run on my Mac with the latest master branch. On Tue, Jun 30, 2015 at 10:55 PM, Sudheesh Katkam wrote: > I had a clean run on my Mac with the latest master this afternoon (and > there are no new commits since then). > > > On Jun 30, 2015, at 9:52 PM, Steven Phillips > wrote:

Re: Time for a 1.1 vote soon?

I had a clean run on my Mac with the latest master this afternoon (and there are no new commits since then). > On Jun 30, 2015, at 9:52 PM, Steven Phillips wrote: > > I just had a clean run on my Linux machine. > > On Tue, Jun 30, 2015 at 9:32 PM, Parth Chandra > wrote: > >> I just complete

Re: Time for a 1.1 vote soon?

I just had a clean run on my Linux machine. On Tue, Jun 30, 2015 at 9:32 PM, Parth Chandra wrote: > I just completed a clean build and test run ( mvn clean install) on my > Mac. > Will try on Linux. > > > > > On Tue, Jun 30, 2015 at 9:24 PM, Jacques Nadeau > wrote: > > > I ran twice more. So

Re: Time for a 1.1 vote soon?

I just completed a clean build and test run ( mvn clean install) on my Mac. Will try on Linux. On Tue, Jun 30, 2015 at 9:24 PM, Jacques Nadeau wrote: > I ran twice more. So here are my three results: > > 1. Errors from previous email. > 2. Tests hung indefinitely (mvn clean install). > 3. I

Re: Time for a 1.1 vote soon?

I ran twice more. So here are my three results: 1. Errors from previous email. 2. Tests hung indefinitely (mvn clean install). 3. I had one test failure, (mvn clean; mvn install), Tests in error: TestSpoolingBuffer.testMultipleExchangesSingleThread:50 » test timed out afte... Is anybody havi

[jira] [Created] (DRILL-3442) Disable install/deployment of distribution tarball to maven repository

Aditya Kishore created DRILL-3442: - Summary: Disable install/deployment of distribution tarball to maven repository Key: DRILL-3442 URL: https://issues.apache.org/jira/browse/DRILL-3442 Project: Apach

Re: ApacheCON EU HBase Track Submissions

Get your submissions in, the deadline is imminent! On Thu, Jun 25, 2015 at 11:44 AM, Nick Dimiduk wrote: > Hello developers, users, speakers, > > In honor of ApacheCON's inaugural "Apache: Big Data" event, I'm hoping to > see a "HBase: NoSQL + SQL" track come together. The idea is to showcase th

Re: Time for a 1.1 vote soon?

I re-ran on my mac and don't see the failures your are seeing. I got one error below related to zookeeper but I believe this is intermittent. $mvn install Tests in error: TestPStoreProviders.verifyZkStore:55 » Runtime Failure while accessing Zookeep... Tests run: 1310, Failures: 0, Error

Re: Time for a 1.1 vote soon?

I'm seeing failures running the build on master on a mac: $ java -version java version "1.7.0_80" Java(TM) SE Runtime Environment (build 1.7.0_80-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) $mvn install ... Failed tests: TestDrillbitResilience.memoryLeaksWhenCancelled

[jira] [Resolved] (DRILL-3437) 2 Listings of Tibco Spotfire Desktop in drop down list

[ https://issues.apache.org/jira/browse/DRILL-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Hahn resolved DRILL-3437. -- Resolution: Fixed > 2 Listings of Tibco Spotfire Desktop in drop down list > ---

[jira] [Resolved] (DRILL-3438) Broken Links in Tibco Spotfire Desktop documentation

[ https://issues.apache.org/jira/browse/DRILL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Hahn resolved DRILL-3438. -- Resolution: Fixed > Broken Links in Tibco Spotfire Desktop documentation > -

Re: Time for a 1.1 vote soon?

Agreed. I'll spin a release. On Tue, Jun 30, 2015 at 6:01 PM, Parth Chandra wrote: > Hey guys, > > Looks like 1.1 is looking fairly good with about 119 issues fixed. I > would recommend we start the release process for 1.1. > > Parth > > On Fri, Jun 26, 2015 at 8:49 AM, Jacques Nadeau > wrot

[jira] [Resolved] (DRILL-3357) Error when adding 2 columns together

[ https://issues.apache.org/jira/browse/DRILL-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3357. --- Resolution: Fixed > Error when adding 2 columns together > ---

[jira] [Resolved] (DRILL-3421) Add new outputformat=json

[ https://issues.apache.org/jira/browse/DRILL-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau resolved DRILL-3421. --- Resolution: Not A Problem > Add new outputformat=json > - > >

Re: Time for a 1.1 vote soon?

Hey guys, Looks like 1.1 is looking fairly good with about 119 issues fixed. I would recommend we start the release process for 1.1. Parth On Fri, Jun 26, 2015 at 8:49 AM, Jacques Nadeau wrote: > Hey Guys, > > Looks like a number things are being wrapped up so it is probably about > time for

[jira] [Created] (DRILL-3441) CompliantTextRecordReader#isStarQuery loops indefinitely

Hanifi Gunes created DRILL-3441: --- Summary: CompliantTextRecordReader#isStarQuery loops indefinitely Key: DRILL-3441 URL: https://issues.apache.org/jira/browse/DRILL-3441 Project: Apache Drill I

[jira] [Created] (DRILL-3440) Canceling queries on Sqlline crashes all Drillbits

Abhishek Girish created DRILL-3440: -- Summary: Canceling queries on Sqlline crashes all Drillbits Key: DRILL-3440 URL: https://issues.apache.org/jira/browse/DRILL-3440 Project: Apache Drill I

Re: SchemaFactory.logger

Jacques Nadeau wrote: Probably my fault. The most common reason is because it used to be an implementation and then got turned into an implementation. Agreed that they should be removed. Roger. I created DRILL-3439 Some interfaces have logger

[jira] [Created] (DRILL-3439) Some interfaces have logger fields.

Daniel Barclay (Drill) created DRILL-3439: - Summary: Some interfaces have logger fields. Key: DRILL-3439 URL: https://issues.apache.org/jira/browse/DRILL-3439 Project: Apache Drill Is

Apache Drill Hangout Information

Hello Drillers, I have created a Google spreadsheet to track leaders of the weekly hangout (Tuesday at 10am Pacific time) to make sure we always have someone able to attend the meeting and facilitate discussion. Commitment is pretty low, for anyone who has attended the hangout it should be easy to

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

You're right, that should be fine. On Jun 30, 2015 4:24 PM, "Abdel Hakim Deneche" wrote: > What would be the impact of making buffer() throw an > OutOfMemoryRuntimeException ? we'll need to change a few places where it > really needs to be handled (like in allocateNewSafe()) but other than that,

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

What would be the impact of making buffer() throw an OutOfMemoryRuntimeException ? we'll need to change a few places where it really needs to be handled (like in allocateNewSafe()) but other than that, just letting the unchecked exception propagate should be fine, and Drill will still display the p

Review Request 36070: DRILL-3243: Need a better error message - Use of alias in window function definition

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36070/ --- Review request for drill and Hanifi Gunes. Bugs: DRILL-3243 https://issues.

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

-I like giving the developer the choice of behavior (thus the two options). It sounds like others are saying to remove this choice (because code is not managing it correctly). I might be misunderstanding the context above but my understanding is that the discussion is not particularly concerned abo

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

Do you think we should be reaching that deep in the other places? On Jun 30, 2015 3:55 PM, "Abdel Hakim Deneche" wrote: > buffer(int) is mostly called from value vectors, but there are an > additional 10+ places where it's being used and most of them don't bother > checking if the returned buffer

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

buffer(int) is mostly called from value vectors, but there are an additional 10+ places where it's being used and most of them don't bother checking if the returned buffer is null. On Tue, Jun 30, 2015 at 3:39 PM, Jacques Nadeau wrote: > What is your sense of the use of this interface? I would h

[jira] [Created] (DRILL-3438) Broken Links in Tibco Spotfire Desktop documentation

Andries Engelbrecht created DRILL-3438: -- Summary: Broken Links in Tibco Spotfire Desktop documentation Key: DRILL-3438 URL: https://issues.apache.org/jira/browse/DRILL-3438 Project: Apache Drill

[jira] [Created] (DRILL-3437) 2 Listings of Tibco Spotfire Desktop in drop down list

Andries Engelbrecht created DRILL-3437: -- Summary: 2 Listings of Tibco Spotfire Desktop in drop down list Key: DRILL-3437 URL: https://issues.apache.org/jira/browse/DRILL-3437 Project: Apache Drill

[jira] [Created] (DRILL-3436) MicroStrategy configuration documentation

Andries Engelbrecht created DRILL-3436: -- Summary: MicroStrategy configuration documentation Key: DRILL-3436 URL: https://issues.apache.org/jira/browse/DRILL-3436 Project: Apache Drill Is

[jira] [Created] (DRILL-3435) Some reserved-keywords require table aliasing

Andy Pernsteiner created DRILL-3435: --- Summary: Some reserved-keywords require table aliasing Key: DRILL-3435 URL: https://issues.apache.org/jira/browse/DRILL-3435 Project: Apache Drill Issu

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

What is your sense of the use of this interface? I would hope new uses would be scarce. Do you think this will be a frequent occurrence that most devs will experience? On Jun 30, 2015 3:35 PM, "Abdel Hakim Deneche" wrote: > I started this discussion while fixing DRILL-3312 >

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34603/ --- (Updated June 30, 2015, 10:37 p.m.) Review request for drill, Jacques Nadeau, J

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

I started this discussion while fixing DRILL-3312 , it took me quite some time to debug and find the root of an error I was seeing. I first thought about fixing those few places that call buffer() without checking if the buffer is null or not, but t

Re: Opposite of FLATTEN

I could write a custom Hive aggregator, but I want to use Drill and get all the performance possible. On Mon, Jun 29, 2015 at 7:02 PM, Venky Kandaswamy wrote: > Couldn¹t you write a custom aggregate function in Hive? (I don¹t have > one). > Thanks, Venky > > On 6/29/15, 6:41 PM, "Ted Dunning"

[jira] [Resolved] (DRILL-3422) Multiple unit test failures on Windows with current master

[ https://issues.apache.org/jira/browse/DRILL-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Kishore resolved DRILL-3422. --- Resolution: Fixed Fix Version/s: 1.1.0 Resolved by [e2e59a0|https://fisheye6.atlassian

[jira] [Created] (DRILL-3434) Applying kvgen on a scalar (field within a map) results in "Unable to get holder type for minor type [LATE] and mode [OPTIONAL]"

Rahul Challapalli created DRILL-3434: Summary: Applying kvgen on a scalar (field within a map) results in "Unable to get holder type for minor type [LATE] and mode [OPTIONAL]" Key: DRILL-3434 URL: https://issu

[jira] [Resolved] (DRILL-3120) Windows startup throws NPE

[ https://issues.apache.org/jira/browse/DRILL-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Kishore resolved DRILL-3120. --- Resolution: Fixed Resolved by [2b5c52e|https://fisheye6.atlassian.com/changelog/incubator-dri

Re: SchemaFactory.logger

Probably my fault. The most common reason is because it used to be an implementation and then got turned into an implementation. Agreed that they should be removed. On Tue, Jun 30, 2015 at 2:42 PM, Daniel Barclay wrote: > Why does _interface_ org.apache.drill.exec.store.SchemaFactory declare a

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

Lots of different comments on this thread. Here are few of my thoughts: I think you need to differentiate the different tiers of interfaces a little bit more. BufferAllocator.buffer() was meant to be a low level advanced interface. It should be used rarely and when done so, only with extreme car

[jira] [Created] (DRILL-3433) DrillConfig.create(Properties) used outside of testing code

Daniel Barclay (Drill) created DRILL-3433: - Summary: DrillConfig.create(Properties) used outside of testing code Key: DRILL-3433 URL: https://issues.apache.org/jira/browse/DRILL-3433 Project:

Re: SchemaFactory.logger

My regex won't capture every case, but it found a decent number of these: interface .*\n.*logger Targets String 'interface .*\n.*logger' Found usages (29 usages found) Unclassified usage (29 usages found) drill-common (4 usages found) org.apache.drill.common.expressi

Re: SchemaFactory.logger

I assume it was added during creation of the file using a template that inserted the logger by default. We should remove it and any other places where it occurs to prevent confusion. On Tue, Jun 30, 2015 at 2:42 PM, Daniel Barclay wrote: > Why does _interface_ org.apache.drill.exec.store.SchemaF

Re: SchemaFactory.logger

I don't think it should. On Tue, Jun 30, 2015 at 2:42 PM, Daniel Barclay wrote: > Why does _interface_ org.apache.drill.exec.store.SchemaFactory declare a > logger? > > Daniel > -- > Daniel Barclay > MapR Technologies > -- Abdelhakim Deneche Software Engineer No

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

> On June 30, 2015, 7:29 p.m., Sudheesh Katkam wrote: > > exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/QueryManager.java, > > line 315 > > > > > > Discussion: Why is this the right thing to do? Is F

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

> On June 30, 2015, 7:29 p.m., Sudheesh Katkam wrote: > > exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/QueryManager.java, > > line 315 > > > > > > Discussion: Why is this the right thing to do? Is F

SchemaFactory.logger

Why does _interface_ org.apache.drill.exec.store.SchemaFactory declare a logger? Daniel -- Daniel Barclay MapR Technologies

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34603/ --- (Updated June 30, 2015, 9:32 p.m.) Review request for drill, Jacques Nadeau, Ja

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

Hanifi GUNES wrote: - We would end up having to add it to almost everything everywhere Why would one propagate the checked exception for no reason? And why would one not propagate the exception for a good reason like robustness? I agree that one has to avoid propagating the checked exception for

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

- We would end up having to add it to almost everything everywhere Why would one propagate the checked exception for no reason? And why would one not propagate the exception for a good reason like robustness? I agree that one has to avoid propagating the checked exception for no reason however I su

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

+1 to Hanifi's On Tue, Jun 30, 2015 at 1:38 PM, Jason Altekruse wrote: > +1 to Hanifi's comments, I think it makes much more sense to have a number > of sites where the operators are explicitly catching a checked OOM > exception and either decide to handle it or produce a message like "Hash > Ag

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

> On June 30, 2015, 7:29 p.m., Sudheesh Katkam wrote: > > exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/Foreman.java, > > line 874 > > > > > > Can you add unit tests in TestDrillbitResilience? what

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

+1 to Hanifi's comments, I think it makes much more sense to have a number of sites where the operators are explicitly catching a checked OOM exception and either decide to handle it or produce a message like "Hash Aggregate does not support our of memory conditions". This would be particularly use

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

> On June 30, 2015, 8:23 p.m., Sudheesh Katkam wrote: > > exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/QueryManager.java, > > line 158 > > > > > > In that case, we know exactly what the status is #g

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

I would resist using a checked exception. We would end up having to add it to almost everything everywhere. Or constantly wrapping it with RuntimeException to get around that; in which case why make it checked to begin with? On Tue, Jun 30, 2015 at 1:28 PM, Hanifi GUNES wrote: > I would propose

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

I would propose throwing a checked exception encouraging explicit and consistent handling of this event. Each sub-system has liberty to decide if an OOM failure is fatal or non-fatal depending on its capabilities. Also if at some point a sub-system needs to communicate with its callers via a differ

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

> On June 30, 2015, 7:29 p.m., Sudheesh Katkam wrote: > > exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/QueryManager.java, > > line 158 > > > > > > Not required? We already log the status > > QueryM

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34603/#review89957 --- exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/Que

[jira] [Resolved] (DRILL-2864) Unable to cast string literal with the valid value in ISO 8601 format to interval

[ https://issues.apache.org/jira/browse/DRILL-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Barclay (Drill) resolved DRILL-2864. --- Resolution: Duplicate Closing as (now-)duplicate because subproblems have been

Re: Review Request 35719: DRILL-3242: Update RPC layer so that requests and response are managed on a secondary thread.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35719/#review89808 --- Initial comments. exec/java-exec/src/main/java/org/apache/drill/ex

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

> On June 30, 2015, 7:29 p.m., Sudheesh Katkam wrote: > > exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/QueryManager.java, > > line 158 > > > > > > Not required? We already log the status > > QueryM

[jira] [Created] (DRILL-3432) Change or document: CAST to interval type doesn't reject non-standard strings

Daniel Barclay (Drill) created DRILL-3432: - Summary: Change or document: CAST to interval type doesn't reject non-standard strings Key: DRILL-3432 URL: https://issues.apache.org/jira/browse/DRILL-3432

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34603/#review89946 --- exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/For

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

I guess that would fix the issue too. But we may still run into situations where the caller will pass a flag to "mute" the exception and not handle the case anyway. If .buffer() unconditionally throws an exception, can't the caller, who wants to, just catch that and handle it properly ? On Tue, J

[jira] [Created] (DRILL-3431) CHAR not handled same as VARCHAR for cast to INTERVAL

Daniel Barclay (Drill) created DRILL-3431: - Summary: CHAR not handled same as VARCHAR for cast to INTERVAL Key: DRILL-3431 URL: https://issues.apache.org/jira/browse/DRILL-3431 Project: Apache

Re: [DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

No, but we should do something close to that. There are cases where the caller can handle the inability to get more memory, and may be able to go to disk. However, you are correct that there are many that can't handle an OOM, and that fail to check. Instead of unconditionally throwing OutOfMemory

[DISCUSSION] should BufferAllocator.buffer() throw an OutOfMemoryException ?

our current implementations of BufferAllocator.buffer(int, int) returns null when it cannot allocate the buffer. But looking through the code, there are many places that don't check if the allocated buffer is null before trying to access it which will throw a NullPointerException. ValueVectors' a

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34603/#review89942 --- exec/java-exec/src/main/java/org/apache/drill/exec/work/foreman/Que

Re: Review Request 34603: DRILL-3167: When a query fails, Foreman should wait for all fragments to finish cleaning up before sending a FAILED state to the client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34603/ --- (Updated June 30, 2015, 6:36 p.m.) Review request for drill, Chris Westin, Jacq

[jira] [Created] (DRILL-3430) CAST to interval type doesn't accept standard-format strings

Daniel Barclay (Drill) created DRILL-3430: - Summary: CAST to interval type doesn't accept standard-format strings Key: DRILL-3430 URL: https://issues.apache.org/jira/browse/DRILL-3430 Project:

[jira] [Created] (DRILL-3429) DrillAvgVarianceConvertlet may produce wrong results while rewriting stddev, variance

Mehant Baid created DRILL-3429: -- Summary: DrillAvgVarianceConvertlet may produce wrong results while rewriting stddev, variance Key: DRILL-3429 URL: https://issues.apache.org/jira/browse/DRILL-3429 Proje

[jira] [Created] (DRILL-3428) Errors during text filereading should provide the file name in the error messge

Parth Chandra created DRILL-3428: Summary: Errors during text filereading should provide the file name in the error messge Key: DRILL-3428 URL: https://issues.apache.org/jira/browse/DRILL-3428 Project

[jira] [Created] (DRILL-3427) Unable to view Drill WEB UI without invoking SQLLINE [bin/sqlline -u jdbc:drill:zk=local] in Embedded Mode

Soumendra Kumar Mishra created DRILL-3427: - Summary: Unable to view Drill WEB UI without invoking SQLLINE [bin/sqlline -u jdbc:drill:zk=local] in Embedded Mode Key: DRILL-3427 URL: https://issues.apache.or

[jira] [Created] (DRILL-3426) DROP Table option not possible whereas DROP View is available

Soumendra Kumar Mishra created DRILL-3426: - Summary: DROP Table option not possible whereas DROP View is available Key: DRILL-3426 URL: https://issues.apache.org/jira/browse/DRILL-3426 Project

[jira] [Created] (DRILL-3425) Drill Queries fetches result set without stating File Name where the searching data found and also how to find number of files available in a Folder which matches the sea

Soumendra Kumar Mishra created DRILL-3425: - Summary: Drill Queries fetches result set without stating File Name where the searching data found and also how to find number of files available in a Folder which matches the search criteria

[jira] [Resolved] (DRILL-3424) Hive Views are not accessible through Drill Query

[ https://issues.apache.org/jira/browse/DRILL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venki Korukanti resolved DRILL-3424. Resolution: Duplicate > Hive Views are not accessible through Drill Query >

[jira] [Created] (DRILL-3424) Hive Views are not accessible through Drill Query

Soumendra Kumar Mishra created DRILL-3424: - Summary: Hive Views are not accessible through Drill Query Key: DRILL-3424 URL: https://issues.apache.org/jira/browse/DRILL-3424 Project: Apache Dril

Hangout starting in 30 minutes

Come join the Apache Drill hangout to find out what is new in the upcoming 1.1 release. Anyone with an interest in Drill is welcome to attend. https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc

[jira] [Created] (DRILL-3423) Add New HTTPD format plugin

Jacques Nadeau created DRILL-3423: - Summary: Add New HTTPD format plugin Key: DRILL-3423 URL: https://issues.apache.org/jira/browse/DRILL-3423 Project: Apache Drill Issue Type: New Feature