[jira] [Resolved] (DRILL-3898) No space error during external sort does not cancel the query

[ https://issues.apache.org/jira/browse/DRILL-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boaz Ben-Zvi resolved DRILL-3898. - Resolution: Fixed Fix Version/s: (was: Future) 1.9.0 Commit ID:

[jira] [Resolved] (DRILL-4771) Drill should avoid doing the same join twice if count(distinct) exists

[ https://issues.apache.org/jira/browse/DRILL-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Kumar Parai resolved DRILL-4771. --- Resolution: Fixed Fix Version/s: 1.9.0 Closed with commit:

Suggest topics for hangout tomorrow (9/20)

I'll start the hangout tomorrow at the usual time. I don't have a set agenda yet but if there are any topics folks wish to discuss, please respond on this thread such that others who might be interested can also join. Thanks.

[jira] [Created] (DRILL-4896) After a failed CTAS, the table both exists and does not exist

Boaz Ben-Zvi created DRILL-4896: --- Summary: After a failed CTAS, the table both exists and does not exist Key: DRILL-4896 URL: https://issues.apache.org/jira/browse/DRILL-4896 Project: Apache Drill

[GitHub] drill pull request #588: Added test cases

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

[GitHub] drill issue #518: DRILL-4653.json - Malformed JSON should not stop the entir...

Github user ssriniva123 commented on the issue: https://github.com/apache/drill/pull/518 Apologize for getting back on this thread late, got tied up with some issues@work. Paul, The json parser is not just a tokenizer, it keeps track of the JSON structure and understands

[GitHub] drill pull request #591: DRILL-3898 : Sort spill was modified to catch all e...

GitHub user Ben-Zvi opened a pull request: https://github.com/apache/drill/pull/591 DRILL-3898 : Sort spill was modified to catch all errors, ignore rep… …eated errors while closing the new group and issue a more detailed error message. See PR history in #585 You can

[GitHub] drill pull request #585: DRILL-3898 : Sort spill was modified to catch all e...

Github user Ben-Zvi closed the pull request at: https://github.com/apache/drill/pull/585 --- 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

Re: ZK lost connectivity issue on large cluster

Hi Sudheesh, If I add selection filter so that no row are returned, the same problem occur. I also simplified the query to include only few integer columns. That particular data repo is ~200+ Billions records spread over ~50 000 parquet files. We have other CSV data repo that are 100x smaller

Re: ZK lost connectivity issue on large cluster

One more interesting thing and another guess to resolve the problem, > P.S.: > We do see this also: > 2016-09-19 14:48:23,444 [drill-executor-9] WARN > o.a.d.exec.rpc.control.WorkEventBus - Fragment ..:1:2 not found in the > work bus. > 2016-09-19 14:48:23,444 [drill-executor-11] WARN >

Re: ZK lost connectivity issue on large cluster

Hi Francois, A simple query with only projections is not an “ideal” use case, since Drill is bound by how fast the client can consume records. There are 1000 scanners sending data to 1 client (vs far fewer scanners sending data in the 12 node case). This might increase the load on the

Re: ZK lost connectivity issue on large cluster

Hi Sudheesh, + Does the query involve any aggregations or filters? Or is this a select query with only projections? Simple query with only projections + Any suspicious timings in the query profile? Nothing specially different than our working query on our small cluster. + Any suspicious