date:20180626

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Prasad Nagaraj Subramanya

Congrats Vitali!

On Tue, Jun 26, 2018 at 7:53 PM shi.chunhui 
wrote:

> Congrats Vitalii!
> --
> Sender:Parth Chandra 
> Sent at:2018 Jun 27 (Wed) 06:23
> To:dev 
> Subject:Re: [ANNOUNCE] New PMC member: Vitalii Diravka
>
> Congratulations Vitalii.
>
> On Tue, Jun 26, 2018 at 12:53 PM, Timothy Farkas  wrote:
>
> > Congrats Vitalii!
> >
> > On Tue, Jun 26, 2018 at 11:12 AM, Aman Sinha 
> wrote:
> >
> > > I am pleased to announce that Drill PMC invited Vitalii Diravka to the
> > PMC
> > > and he has accepted the invitation.
> > >
> > > Congratulations Vitalii and thanks for your contributions !
> > >
> > > -Aman
> > > (on behalf of Drill PMC)
> > >
> >
>

Re: Drill Hangout tomorrow 06/26

2018-06-26 Thread Padma Penumarthy

Here is the link to the document. Any feedback/comments welcome.

https://docs.google.com/document/d/1Z-67Y_KNcbA2YYWCHEwf2PUEmXRPWSXsw-CHnXW_98Q/edit?usp=sharing

Thanks
Padma

On Jun 26, 2018, at 12:12 PM, Aman Sinha
mailto:amansi...@gmail.com>> wrote:

Hangout attendees on 06/26:
Padma, Hanumath, Boaz, Aman, Jyothsna, Sorabh, Arina, Bohdan, Vitalii,
Volodymyr, Abhishek, Robert

2 topics were discussed:
1. Vitalii brought up the Travis timeout issue for which he has sent out
an email in this thread; Actually Vitalli can you send it in a separate
email with explicit subject otherwise people may miss it.
2. Padma went over the batch sizing work and current status. Padma, pls
add a link to your document. Summarizing some of the discussion:

- Does batch sizing affect output batches only or internal batches also
? For certain operators such as HashAgg it does affect the internal
batches held in the hash table since these batches are transferred as-is to
the output container.
- 16 MB limit on the batch size is a best effort but in some cases it
could slightly exceed. The number of rows per output batch is estimated as
nearest lower power of 2. For example, if based on input batch size, the
number of output rows is 600, it will be rounded down to 512.
- An optimization could be done in future to have upstream operator
provide the batch size information in metadata instead of downstream
operator computing it for each incoming.
- There was discussion on estimating the size of complex type columns
especially ones with nesting levels. It would be good to add details in
the document.

-Aman

On Tue, Jun 26, 2018 at 10:48 AM Vitalii Diravka
mailto:vitalii.dira...@gmail.com>>
wrote:

Lately Drill Travis Build fails more often because of Travis job time
expires.
The right way is to accelerate Drill execution :)

Nevertheless I believe we should consider excluding some more tests from
Travis Build.
We can add all TPCH tests (
TestTpchLimit0, TestTpchExplain, TestTpchPlanning, TestTpchExplain) to the
SlowTest category.

Is there other solution for this issue? What are other tests are executed
very slowly?

Kind regards
Vitalii

On Tue, Jun 26, 2018 at 3:34 AM Aman Sinha
mailto:amansi...@apache.org>> wrote:

We'll have the Drill hangout tomorrow Jun26th, 2018 at 10:00 PDT.

If you have any topics to discuss, send a reply to this post or just join
the hangout.

( Drill hangout link

)

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread shi.chunhui

Congrats Vitalii!
--
Sender:Parth Chandra 
Sent at:2018 Jun 27 (Wed) 06:23
To:dev 
Subject:Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Congratulations Vitalii.

On Tue, Jun 26, 2018 at 12:53 PM, Timothy Farkas  wrote:

> Congrats Vitalii!
>
> On Tue, Jun 26, 2018 at 11:12 AM, Aman Sinha  wrote:
>
> > I am pleased to announce that Drill PMC invited Vitalii Diravka to the
> PMC
> > and he has accepted the invitation.
> >
> > Congratulations Vitalii and thanks for your contributions !
> >
> > -Aman
> > (on behalf of Drill PMC)
> >
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Robert Hou

Congrats, Vitalii!

--Robert

On Tue, Jun 26, 2018 at 6:17 PM, Padma Penumarthy 
wrote:

> Congrats Vitalii.
>
> Thanks
> Padma
>
>
> > On Jun 26, 2018, at 6:14 PM, Vlad Rozov  wrote:
> >
> > Congratulations Vitalii!
> >
> > Thank you,
> >
> > Vlad
> >
> > On 6/26/18 17:11, Paul Rogers wrote:
> >> Congratulations Vitalii!
> >> - Paul
> >>
> >>
> >> On Tuesday, June 26, 2018, 11:12:16 AM PDT, Aman Sinha <
> amansi...@apache.org> wrote:
> >>I am pleased to announce that Drill PMC invited Vitalii Diravka to
> the PMC
> >> and he has accepted the invitation.
> >>
> >> Congratulations Vitalii and thanks for your contributions !
> >>
> >> -Aman
> >> (on behalf of Drill PMC)
> >>
> >
>
>

Re: Apache drill show a lot of CLOSE_WAIT states when we access https://ip address:8047

2018-06-26 Thread Vlad Rozov

By itself CLOSE_WAIT state does not indicate a problem. Check jstack of 
the Drillbit and Jetty worker threads in particular. Try increasing 
drill.exec.http.jetty.server.selector setting.


Thank you,

Vlad

On 6/26/18 01:26, Ken Qi (Guangquan) wrote:

Hi Team,

Hope all is good.

We need your help.

Here is the apache drill process which we installed in our server.

drill19220 1 17 16:48 ?00:15:32 /usr/java/jdk/bin/java
-Xms8G -Xmx8G -XX:MaxDirectMemorySize=96G -XX:ReservedCodeCacheSize=1024m
-Ddrill.exec.enable-epoll=false -XX:+CMSClassUnloadingEnabled -XX:+UseG1GC
-Dlog.path=/var/log/drill/drillbit.log
-Dlog.query.path=/var/log/drill/drillbit_queries.json -cp
/usr/local/apache-drill-1.13.1/conf:/usr/local/apache-drill-1.13.1/jars/*:/usr/local/apache-drill-1.13.1/jars/ext/*:/usr/local/apache-drill-1.13.1/jars/3rdparty/*:/usr/local/apache-drill-1.13.1/jars/classb/*:/usr/local/apache-drill-1.13.1/jars/3rdparty/linux/*
org.apache.drill.exec.server.Drillbit
root 23651 23227  0 18:16 pts/100:00:00 grep --color=auto java

Question 1:

There are a lot of CLOSE_WAIT states when I access apache drill  https://ip
address:8047   I have changed
our server ip to  for the secruity reason, this caused that we can't
access apache drill by  https://ip address:8047
, so we can't check which SQL
run failed.

tcp6   0  0 :::8047 :::*LISTEN
 19220/java
tcp6 518  0 192.168.:8047  192.168.100.131:54132
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.100.222:52986
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53009
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54131
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:61202
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54366
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54129
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:58627
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:58486
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54134
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53008
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:56226
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:52991
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:51172
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:36136
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54133
  CLOSE_WAIT  19220/java
tcp6  24  0 192.168.  :8047  192.168.100.131:57474
  ESTABLISHED 19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54069
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54130
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53001
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:52985
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:52990
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54212
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.100.131:58628
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.100.131:53955
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:57391
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:41219
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54307
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53000
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168  :8047  192.168.100.222:52984
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54308
  CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:46189
  CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54211
  CLOSE_WAIT  19220/java



Question 2


Our apache drill was down frequently, it seems that it is due to memory
leak. However, we have configured 96G memory for apache dirll, so can you
please advise how can we identify which SQL took a lot of memory? and how
can improve our performance?


Error Id: 40d789a6-91ee-4e0b-bfc9-a26358a43df3 on
theremin.root.digitalalchemy:31010]
org.apache.drill.common.exceptions.UserException: SYSTEM ERROR:
IllegalStateException: Memory was le

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Padma Penumarthy

Congrats Vitalii.

Thanks
Padma


> On Jun 26, 2018, at 6:14 PM, Vlad Rozov  wrote:
> 
> Congratulations Vitalii!
> 
> Thank you,
> 
> Vlad
> 
> On 6/26/18 17:11, Paul Rogers wrote:
>> Congratulations Vitalii!
>> - Paul
>> 
>>  
>> On Tuesday, June 26, 2018, 11:12:16 AM PDT, Aman Sinha 
>>  wrote:
>>I am pleased to announce that Drill PMC invited Vitalii Diravka to the PMC
>> and he has accepted the invitation.
>> 
>> Congratulations Vitalii and thanks for your contributions !
>> 
>> -Aman
>> (on behalf of Drill PMC)
>>   
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Vlad Rozov


Congratulations Vitalii!

Thank you,

Vlad

On 6/26/18 17:11, Paul Rogers wrote:

Congratulations Vitalii!
- Paul

  


 On Tuesday, June 26, 2018, 11:12:16 AM PDT, Aman Sinha 
 wrote:
  
  I am pleased to announce that Drill PMC invited Vitalii Diravka to the PMC

and he has accepted the invitation.

Congratulations Vitalii and thanks for your contributions !

-Aman
(on behalf of Drill PMC)

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread weijie tong

Congratulations Vitalii!

On Wed, Jun 27, 2018 at 8:11 AM Paul Rogers 
wrote:

> Congratulations Vitalii!
> - Paul
>
>
>
> On Tuesday, June 26, 2018, 11:12:16 AM PDT, Aman Sinha <
> amansi...@apache.org> wrote:
>
>  I am pleased to announce that Drill PMC invited Vitalii Diravka to the PMC
> and he has accepted the invitation.
>
> Congratulations Vitalii and thanks for your contributions !
>
> -Aman
> (on behalf of Drill PMC)
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Paul Rogers

Congratulations Vitalii!
- Paul

 

On Tuesday, June 26, 2018, 11:12:16 AM PDT, Aman Sinha 
 wrote:  
 
 I am pleased to announce that Drill PMC invited Vitalii Diravka to the PMC
and he has accepted the invitation.

Congratulations Vitalii and thanks for your contributions !

-Aman
(on behalf of Drill PMC)

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Karthikeyan Manivannan

Congrats Vitalii!

On Tue, Jun 26, 2018 at 3:23 PM, Parth Chandra  wrote:

> Congratulations Vitalii.
>
> On Tue, Jun 26, 2018 at 12:53 PM, Timothy Farkas  wrote:
>
> > Congrats Vitalii!
> >
> > On Tue, Jun 26, 2018 at 11:12 AM, Aman Sinha 
> wrote:
> >
> > > I am pleased to announce that Drill PMC invited Vitalii Diravka to the
> > PMC
> > > and he has accepted the invitation.
> > >
> > > Congratulations Vitalii and thanks for your contributions !
> > >
> > > -Aman
> > > (on behalf of Drill PMC)
> > >
> >
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Parth Chandra

Congratulations Vitalii.

On Tue, Jun 26, 2018 at 12:53 PM, Timothy Farkas  wrote:

> Congrats Vitalii!
>
> On Tue, Jun 26, 2018 at 11:12 AM, Aman Sinha  wrote:
>
> > I am pleased to announce that Drill PMC invited Vitalii Diravka to the
> PMC
> > and he has accepted the invitation.
> >
> > Congratulations Vitalii and thanks for your contributions !
> >
> > -Aman
> > (on behalf of Drill PMC)
> >
>

Re: Help with Apache Drill - S3 compatible storage connectivity

2018-06-26 Thread Saurabh Mahapatra

I mean seriously. Dummy id? 

Sent from my iPhone



> On Jun 26, 2018, at 11:30 AM, dummy id  wrote:
> 
> Can i get an update on this please?
> 
>> On Fri, Jun 15, 2018 at 11:36 AM, dummy id  wrote:
>> 
>> *Team, *
>> 
>> 
>> 
>> *I am not sure who can help me out with this, so just adding both of the
>> help community..I have followed your  documentation on setting up drill and
>> i am able to query the files from local , meaning class path and dfs, but
>> not able to do it with s3. I am not using Amazon S3 instead i am using S3
>> compatible storage from DELL EMC. I would need your help in setting up the
>> storage plugin file so that it uses path style addressing instead of normal
>> URL method. I would request you to kindly share an example core-site.xml
>> file as well as an example storage plugin file where it uses path style
>> addressing method to connect to s3.*
>> 
>> 
>> 
>> *I have tried using fs**.**s3a**.**path**.**style**.**access with
>> value true in both core-site and storage plugin files, but still the path
>> style addressing is not being read by drill and it again tries to connect
>> using URL method as it uses in connecting with Amazon S3. Kindly help..*
>> 
>> 
>> 
>> *Just an FYI, i have followed steps from "Drill in 10 minutes"
>> documentation to install and connect with my S3 compatible storage.*
>> 
>> 
>> 
>> *Awaiting for your reply..*
>> 
>> 
>>

Re: Help with Apache Drill - S3 compatible storage connectivity

2018-06-26 Thread dummy id

Can i get an update on this please?

On Fri, Jun 15, 2018 at 11:36 AM, dummy id  wrote:

> *Team, *
>
>
>
> *I am not sure who can help me out with this, so just adding both of the
> help community..I have followed your  documentation on setting up drill and
> i am able to query the files from local , meaning class path and dfs, but
> not able to do it with s3. I am not using Amazon S3 instead i am using S3
> compatible storage from DELL EMC. I would need your help in setting up the
> storage plugin file so that it uses path style addressing instead of normal
> URL method. I would request you to kindly share an example core-site.xml
> file as well as an example storage plugin file where it uses path style
> addressing method to connect to s3.*
>
>
>
> *I have tried using fs**.**s3a**.**path**.**style**.**access with
> value true in both core-site and storage plugin files, but still the path
> style addressing is not being read by drill and it again tries to connect
> using URL method as it uses in connecting with Amazon S3. Kindly help..*
>
>
>
> *Just an FYI, i have followed steps from "Drill in 10 minutes"
> documentation to install and connect with my S3 compatible storage.*
>
>
>
> *Awaiting for your reply..*
>
>
>

[jira] [Created] (DRILL-6543) Options for memory mgmt: Reserve allowance for non-buffered, and Hash-Join default to not fallback

2018-06-26 Thread Boaz Ben-Zvi (JIRA)

Boaz Ben-Zvi created DRILL-6543:
---

 Summary: Options for memory mgmt: Reserve allowance for 
non-buffered, and Hash-Join default to not fallback   
 Key: DRILL-6543
 URL: https://issues.apache.org/jira/browse/DRILL-6543
 Project: Apache Drill
  Issue Type: Improvement
  Components: Execution - Relational Operators
Affects Versions: 1.13.0
Reporter: Boaz Ben-Zvi
Assignee: Boaz Ben-Zvi
 Fix For: 1.14.0


Changes to options related to memory budgeting:

(1) Change the default for "drill.exec.hashjoin.fallback.enabled" to *false* 
(same as for the similar Hash-Agg option). This would force users to calculate 
and assign sufficient memory for the query, or explicitly choose to fallback.

(2) When the "planner.memory.max_query_memory_per_node" (MQMPN) option is set 
equal (or "nearly equal") to the allocated *Direct Memory*, an OOM is still 
possible. The reason is that the memory used by the "non-buffered" operators is 
not taken into account.

For example, MQMPN == Direct-Memory == 100 MB. Run a query with 5 buffered 
operators (e.g., 5 instances of a Hash-Join), so each gets "promised" 20 MB. 
When other non-buffered operators (e.g., a Scanner, or a Sender) also grab some 
of the Direct Memory, then less than 100 MB is left available. And if all those 
5 Hash-Joins are pushing their limits, then one HJ may have only allocated 12MB 
so far, but on the next 1MB allocation it will hit an OOM (from the JVM, as all 
the 100MB Direct memory is already used).

A solution -- a new option to _*reserve*_ some of the Direct Memory for those 
non-buffered operators (e.g., default %25). This *allowance* may prevent many 
of the cases like the example above. The new option would return an error (when 
a query initiates) if the MQMPN is set too high. Note that this option +can 
not+ address concurrent queries.

This should also apply to the alternative for the MQMPN - the 
{{"planner.memory.percent_per_query"}} option (PPQ). The PPQ does not 
_*reserve*_ such memory (e.g., can set it to %100); only its documentation 
clearly explains this issue (that doc suggests reserving %50 allowance, as it 
was written when the Hash-Join was non-buffered; i.e., before spill was 
implemented).

The memory given to the buffered operators is the highest calculated between 
the MQMPN and the PPQ. The new reserve option would verify that this figure 
allows the allowance.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Timothy Farkas

Congrats Vitalii!

On Tue, Jun 26, 2018 at 11:12 AM, Aman Sinha  wrote:

> I am pleased to announce that Drill PMC invited Vitalii Diravka to the PMC
> and he has accepted the invitation.
>
> Congratulations Vitalii and thanks for your contributions !
>
> -Aman
> (on behalf of Drill PMC)
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Hanumath Rao Maduri

Congratulations Vitalii!

On Tue, Jun 26, 2018 at 12:27 PM, Gautam Parai  wrote:

> Congratulations Vitalii!
>
> Gautam
>
> On Tue, Jun 26, 2018 at 11:48 AM, Volodymyr Vysotskyi <
> volody...@apache.org>
> wrote:
>
> >  Congratulations, Vitalii!
> >
> > Kind regards,
> > Volodymyr Vysotskyi
> >
> >
> > вт, 26 черв. 2018 о 21:38 Robert Wu  пише:
> >
> > > Congratulations, Vitalii!
> > >
> > > Best regards,
> > >
> > > Rob
> > >
> > > -Original Message-
> > > From: Sorabh Hamirwasia 
> > > Sent: Tuesday, June 26, 2018 11:30 AM
> > > To: dev@drill.apache.org
> > > Subject: Re: [ANNOUNCE] New PMC member: Vitalii Diravka
> > >
> > > Congratulations Vitalii!
> > >
> > > Thanks,
> > > Sorabh
> > >
> > > On Tue, Jun 26, 2018 at 11:18 AM, Arina Yelchiyeva <
> > > arina.yelchiy...@gmail.com> wrote:
> > >
> > > > Congratulations, Vitalii! Well deserved!
> > > >
> > > > Kind regards,
> > > > Arina
> > > >
> > > > On Tue, Jun 26, 2018 at 9:16 PM Bridget Bevens 
> > wrote:
> > > >
> > > > > Congratulations, Vitalii!
> > > > >
> > > > > On Tue, Jun 26, 2018 at 11:14 AM, Abhishek Girish
> > > > > 
> > > > > wrote:
> > > > >
> > > > > > Congratulations, Vitalii!
> > > > > >
> > > > > > On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha <
> amansi...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > I am pleased to announce that Drill PMC invited Vitalii Diravka
> > > > > > > to
> > > > the
> > > > > > PMC
> > > > > > > and he has accepted the invitation.
> > > > > > >
> > > > > > > Congratulations Vitalii and thanks for your contributions !
> > > > > > >
> > > > > > > -Aman
> > > > > > > (on behalf of Drill PMC)
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

[jira] [Created] (DRILL-6542) IndexOutOfBoundsException for multilevel lateral queries with schema changed partitioned complex data

2018-06-26 Thread Kedar Sankar Behera (JIRA)

Kedar Sankar Behera created DRILL-6542:
--

 Summary: IndexOutOfBoundsException for multilevel lateral queries 
with schema changed partitioned complex data
 Key: DRILL-6542
 URL: https://issues.apache.org/jira/browse/DRILL-6542
 Project: Apache Drill
  Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Kedar Sankar Behera
 Fix For: 1.14.0


IndexOutOfBoundsException for multilevel lateral queries with schema changed 
partitioned complex data
query:
{code}
select customer.c_custkey, customer.c_name, orders.orderkey, orders.totalprice, 
olineitems.l_partkey, olineitems.l_linenumber, olineitems.l_quantity from 
customer, 
lateral (select t1.o.o_orderkey as orderkey, t1.o.o_totalprice as totalprice, 
t1.o.o_lineitems as lineitems from unnest(customer.c_orders) t1(o)) orders, 
lateral (select t2.l.l_partkey as l_partkey, t2.l.l_linenumber as l_linenumber, 
t2.l.l_quantity as l_quantity from unnest(orders.lineitems) t2(l)) olineitems 
order by customer.c_custkey, orders.orderkey, orders.totalprice, 
olineitems.l_partkey, olineitems.l_linenumber, olineitems.l_quantity limit 50;
{code}

Error:
{code}
[Error Id: 7427fa7e-af4a-4f11-acd9-ced71848a1ed on drill182:31010]
org.apache.drill.common.exceptions.UserException: SYSTEM ERROR: 
IndexOutOfBoundsException: writerIndex: 1 (expected: readerIndex(0) <= 
writerIndex <= capacity(0))

Fragment 0:0

[Error Id: 7427fa7e-af4a-4f11-acd9-ced71848a1ed on drill182:31010]
 at 
org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:633)
 ~[drill-common-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.work.fragment.FragmentExecutor.sendFinalState(FragmentExecutor.java:361)
 [drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.work.fragment.FragmentExecutor.cleanup(FragmentExecutor.java:216)
 [drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.work.fragment.FragmentExecutor.run(FragmentExecutor.java:327)
 [drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.common.SelfCleaningRunnable.run(SelfCleaningRunnable.java:38) 
[drill-common-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[na:1.8.0_161]
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[na:1.8.0_161]
 at java.lang.Thread.run(Thread.java:748) [na:1.8.0_161]
Caused by: java.lang.IndexOutOfBoundsException: writerIndex: 1 (expected: 
readerIndex(0) <= writerIndex <= capacity(0))
 at io.netty.buffer.AbstractByteBuf.writerIndex(AbstractByteBuf.java:104) 
~[netty-buffer-4.0.48.Final.jar:4.0.48.Final]
 at 
org.apache.drill.exec.vector.UInt1Vector.splitAndTransferTo(UInt1Vector.java:329)
 ~[vector-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.vector.NullableBigIntVector.splitAndTransferTo(NullableBigIntVector.java:312)
 ~[vector-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.vector.NullableBigIntVector$TransferImpl.splitAndTransfer(NullableBigIntVector.java:339)
 ~[vector-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.vector.complex.RepeatedMapVector$SingleMapTransferPair.splitAndTransfer(RepeatedMapVector.java:298)
 ~[vector-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.physical.impl.unnest.UnnestImpl.unnestRecords(UnnestImpl.java:101)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.physical.impl.unnest.UnnestRecordBatch.doWork(UnnestRecordBatch.java:283)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.physical.impl.unnest.UnnestRecordBatch.innerNext(UnnestRecordBatch.java:236)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.record.AbstractRecordBatch.next(AbstractRecordBatch.java:172)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.record.AbstractRecordBatch.next(AbstractRecordBatch.java:119)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.record.AbstractRecordBatch.next(AbstractRecordBatch.java:109)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.record.AbstractUnaryRecordBatch.innerNext(AbstractUnaryRecordBatch.java:63)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.innerNext(ProjectRecordBatch.java:137)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.record.AbstractRecordBatch.next(AbstractRecordBatch.java:172)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.record.AbstractRecordBatch.next(AbstractRecordBatch.java:119)
 ~[drill-java-exec-1.14.0-SNAPSHOT.jar:1.14.0-SNAPSHOT]
 at 
org.apache.drill.exec.physical.impl.join.LateralJoinBatch.processRightB

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Gautam Parai

Congratulations Vitalii!

Gautam

On Tue, Jun 26, 2018 at 11:48 AM, Volodymyr Vysotskyi 
wrote:

>  Congratulations, Vitalii!
>
> Kind regards,
> Volodymyr Vysotskyi
>
>
> вт, 26 черв. 2018 о 21:38 Robert Wu  пише:
>
> > Congratulations, Vitalii!
> >
> > Best regards,
> >
> > Rob
> >
> > -Original Message-
> > From: Sorabh Hamirwasia 
> > Sent: Tuesday, June 26, 2018 11:30 AM
> > To: dev@drill.apache.org
> > Subject: Re: [ANNOUNCE] New PMC member: Vitalii Diravka
> >
> > Congratulations Vitalii!
> >
> > Thanks,
> > Sorabh
> >
> > On Tue, Jun 26, 2018 at 11:18 AM, Arina Yelchiyeva <
> > arina.yelchiy...@gmail.com> wrote:
> >
> > > Congratulations, Vitalii! Well deserved!
> > >
> > > Kind regards,
> > > Arina
> > >
> > > On Tue, Jun 26, 2018 at 9:16 PM Bridget Bevens 
> wrote:
> > >
> > > > Congratulations, Vitalii!
> > > >
> > > > On Tue, Jun 26, 2018 at 11:14 AM, Abhishek Girish
> > > > 
> > > > wrote:
> > > >
> > > > > Congratulations, Vitalii!
> > > > >
> > > > > On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha 
> > > > wrote:
> > > > >
> > > > > > I am pleased to announce that Drill PMC invited Vitalii Diravka
> > > > > > to
> > > the
> > > > > PMC
> > > > > > and he has accepted the invitation.
> > > > > >
> > > > > > Congratulations Vitalii and thanks for your contributions !
> > > > > >
> > > > > > -Aman
> > > > > > (on behalf of Drill PMC)
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Drill Hangout tomorrow 06/26

2018-06-26 Thread Aman Sinha

Hangout attendees on 06/26:
Padma, Hanumath, Boaz, Aman, Jyothsna, Sorabh, Arina, Bohdan, Vitalii,
Volodymyr, Abhishek, Robert

2 topics were discussed:
1.  Vitalii brought up the Travis timeout issue for which he has sent out
an email in this thread;  Actually Vitalli can you send it in a separate
email with explicit subject otherwise people may miss it.
2. Padma went over the batch sizing work and current status.  Padma, pls
add a link to your document.  Summarizing some of the discussion:

   - Does batch sizing affect output batches only or internal batches also
   ?  For certain operators such as HashAgg it does affect the internal
   batches held in the hash table since these batches are transferred as-is to
   the output container.
   - 16 MB limit on the batch size is a best effort but in some cases it
   could slightly exceed.  The number of rows per output batch is estimated as
   nearest lower power of 2.  For example, if based on input batch size, the
   number of output rows is 600, it will be rounded down to 512.
   - An optimization could be done in future to have upstream operator
   provide the batch size information in metadata instead of downstream
   operator computing it for each incoming.
   - There was discussion on estimating the size of complex type columns
   especially ones with nesting levels.  It would be good to add details in
   the document.


-Aman

On Tue, Jun 26, 2018 at 10:48 AM Vitalii Diravka 
wrote:

> Lately Drill Travis Build fails more often because of Travis job time
> expires.
> The right way is to accelerate Drill execution :)
>
> Nevertheless I believe we should consider excluding some more tests from
> Travis Build.
> We can add all TPCH tests (
> TestTpchLimit0, TestTpchExplain, TestTpchPlanning, TestTpchExplain) to the
> SlowTest category.
>
> Is there other solution for this issue? What are other tests are executed
> very slowly?
>
> Kind regards
> Vitalii
>
>
> On Tue, Jun 26, 2018 at 3:34 AM Aman Sinha  wrote:
>
> > We'll have the Drill hangout tomorrow Jun26th, 2018 at 10:00 PDT.
> >
> > If you have any topics to discuss, send a reply to this post or just join
> > the hangout.
> >
> > ( Drill hangout link
> >  )
> >
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Volodymyr Vysotskyi

 Congratulations, Vitalii!

Kind regards,
Volodymyr Vysotskyi


вт, 26 черв. 2018 о 21:38 Robert Wu  пише:

> Congratulations, Vitalii!
>
> Best regards,
>
> Rob
>
> -Original Message-
> From: Sorabh Hamirwasia 
> Sent: Tuesday, June 26, 2018 11:30 AM
> To: dev@drill.apache.org
> Subject: Re: [ANNOUNCE] New PMC member: Vitalii Diravka
>
> Congratulations Vitalii!
>
> Thanks,
> Sorabh
>
> On Tue, Jun 26, 2018 at 11:18 AM, Arina Yelchiyeva <
> arina.yelchiy...@gmail.com> wrote:
>
> > Congratulations, Vitalii! Well deserved!
> >
> > Kind regards,
> > Arina
> >
> > On Tue, Jun 26, 2018 at 9:16 PM Bridget Bevens  wrote:
> >
> > > Congratulations, Vitalii!
> > >
> > > On Tue, Jun 26, 2018 at 11:14 AM, Abhishek Girish
> > > 
> > > wrote:
> > >
> > > > Congratulations, Vitalii!
> > > >
> > > > On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha 
> > > wrote:
> > > >
> > > > > I am pleased to announce that Drill PMC invited Vitalii Diravka
> > > > > to
> > the
> > > > PMC
> > > > > and he has accepted the invitation.
> > > > >
> > > > > Congratulations Vitalii and thanks for your contributions !
> > > > >
> > > > > -Aman
> > > > > (on behalf of Drill PMC)
> > > > >
> > > >
> > >
> >
>

RE: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Robert Wu

Congratulations, Vitalii!

Best regards,

Rob

-Original Message-
From: Sorabh Hamirwasia  
Sent: Tuesday, June 26, 2018 11:30 AM
To: dev@drill.apache.org
Subject: Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Congratulations Vitalii!

Thanks,
Sorabh

On Tue, Jun 26, 2018 at 11:18 AM, Arina Yelchiyeva < 
arina.yelchiy...@gmail.com> wrote:

> Congratulations, Vitalii! Well deserved!
>
> Kind regards,
> Arina
>
> On Tue, Jun 26, 2018 at 9:16 PM Bridget Bevens  wrote:
>
> > Congratulations, Vitalii!
> >
> > On Tue, Jun 26, 2018 at 11:14 AM, Abhishek Girish 
> > 
> > wrote:
> >
> > > Congratulations, Vitalii!
> > >
> > > On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha 
> > wrote:
> > >
> > > > I am pleased to announce that Drill PMC invited Vitalii Diravka 
> > > > to
> the
> > > PMC
> > > > and he has accepted the invitation.
> > > >
> > > > Congratulations Vitalii and thanks for your contributions !
> > > >
> > > > -Aman
> > > > (on behalf of Drill PMC)
> > > >
> > >
> >
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Sorabh Hamirwasia

Congratulations Vitalii!

Thanks,
Sorabh

On Tue, Jun 26, 2018 at 11:18 AM, Arina Yelchiyeva <
arina.yelchiy...@gmail.com> wrote:

> Congratulations, Vitalii! Well deserved!
>
> Kind regards,
> Arina
>
> On Tue, Jun 26, 2018 at 9:16 PM Bridget Bevens  wrote:
>
> > Congratulations, Vitalii!
> >
> > On Tue, Jun 26, 2018 at 11:14 AM, Abhishek Girish 
> > wrote:
> >
> > > Congratulations, Vitalii!
> > >
> > > On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha 
> > wrote:
> > >
> > > > I am pleased to announce that Drill PMC invited Vitalii Diravka to
> the
> > > PMC
> > > > and he has accepted the invitation.
> > > >
> > > > Congratulations Vitalii and thanks for your contributions !
> > > >
> > > > -Aman
> > > > (on behalf of Drill PMC)
> > > >
> > >
> >
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Arina Yelchiyeva

Congratulations, Vitalii! Well deserved!

Kind regards,
Arina

On Tue, Jun 26, 2018 at 9:16 PM Bridget Bevens  wrote:

> Congratulations, Vitalii!
>
> On Tue, Jun 26, 2018 at 11:14 AM, Abhishek Girish 
> wrote:
>
> > Congratulations, Vitalii!
> >
> > On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha 
> wrote:
> >
> > > I am pleased to announce that Drill PMC invited Vitalii Diravka to the
> > PMC
> > > and he has accepted the invitation.
> > >
> > > Congratulations Vitalii and thanks for your contributions !
> > >
> > > -Aman
> > > (on behalf of Drill PMC)
> > >
> >
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Bridget Bevens

Congratulations, Vitalii!

On Tue, Jun 26, 2018 at 11:14 AM, Abhishek Girish 
wrote:

> Congratulations, Vitalii!
>
> On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha  wrote:
>
> > I am pleased to announce that Drill PMC invited Vitalii Diravka to the
> PMC
> > and he has accepted the invitation.
> >
> > Congratulations Vitalii and thanks for your contributions !
> >
> > -Aman
> > (on behalf of Drill PMC)
> >
>

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Abhishek Girish

Congratulations, Vitalii!

On Tue, Jun 26, 2018 at 11:12 AM Aman Sinha  wrote:

> I am pleased to announce that Drill PMC invited Vitalii Diravka to the PMC
> and he has accepted the invitation.
>
> Congratulations Vitalii and thanks for your contributions !
>
> -Aman
> (on behalf of Drill PMC)
>

[ANNOUNCE] New PMC member: Vitalii Diravka

2018-06-26 Thread Aman Sinha

I am pleased to announce that Drill PMC invited Vitalii Diravka to the PMC
and he has accepted the invitation.

Congratulations Vitalii and thanks for your contributions !

-Aman
(on behalf of Drill PMC)

Re: Drill Hangout tomorrow 06/26

2018-06-26 Thread Vitalii Diravka

Lately Drill Travis Build fails more often because of Travis job time
expires.
The right way is to accelerate Drill execution :)

Nevertheless I believe we should consider excluding some more tests from
Travis Build.
We can add all TPCH tests (
TestTpchLimit0, TestTpchExplain, TestTpchPlanning, TestTpchExplain) to the
SlowTest category.

Is there other solution for this issue? What are other tests are executed
very slowly?

Kind regards
Vitalii

On Tue, Jun 26, 2018 at 3:34 AM Aman Sinha  wrote:

> We'll have the Drill hangout tomorrow Jun26th, 2018 at 10:00 PDT.
>
> If you have any topics to discuss, send a reply to this post or just join
> the hangout.
>
> ( Drill hangout link
>  )
>

Apache drill show a lot of CLOSE_WAIT states when we access https://ip address:8047

2018-06-26 Thread Ken Qi (Guangquan)

Hi Team,

Hope all is good.

We need your help.

Here is the apache drill process which we installed in our server.

drill19220 1 17 16:48 ?00:15:32 /usr/java/jdk/bin/java
-Xms8G -Xmx8G -XX:MaxDirectMemorySize=96G -XX:ReservedCodeCacheSize=1024m
-Ddrill.exec.enable-epoll=false -XX:+CMSClassUnloadingEnabled -XX:+UseG1GC
-Dlog.path=/var/log/drill/drillbit.log
-Dlog.query.path=/var/log/drill/drillbit_queries.json -cp
/usr/local/apache-drill-1.13.1/conf:/usr/local/apache-drill-1.13.1/jars/*:/usr/local/apache-drill-1.13.1/jars/ext/*:/usr/local/apache-drill-1.13.1/jars/3rdparty/*:/usr/local/apache-drill-1.13.1/jars/classb/*:/usr/local/apache-drill-1.13.1/jars/3rdparty/linux/*
org.apache.drill.exec.server.Drillbit
root 23651 23227  0 18:16 pts/100:00:00 grep --color=auto java

Question 1:

There are a lot of CLOSE_WAIT states when I access apache drill  https://ip
address:8047   I have changed
our server ip to  for the secruity reason, this caused that we can't
access apache drill by  https://ip address:8047
, so we can't check which SQL
run failed.

tcp6   0  0 :::8047 :::*LISTEN
19220/java
tcp6 518  0 192.168.:8047  192.168.100.131:54132
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.100.222:52986
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53009
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54131
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:61202
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54366
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54129
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:58627
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:58486
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54134
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53008
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:56226
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:52991
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:51172
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:36136
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54133
 CLOSE_WAIT  19220/java
tcp6  24  0 192.168.  :8047  192.168.100.131:57474
 ESTABLISHED 19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54069
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54130
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53001
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:52985
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:52990
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54212
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.100.131:58628
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.100.131:53955
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:57391
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:41219
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54307
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.222:53000
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168  :8047  192.168.100.222:52984
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54308
 CLOSE_WAIT  19220/java
tcp6   1  0 192.168.  :8047  192.168.3.119:46189
 CLOSE_WAIT  19220/java
tcp6 518  0 192.168.  :8047  192.168.100.131:54211
 CLOSE_WAIT  19220/java



Question 2


Our apache drill was down frequently, it seems that it is due to memory
leak. However, we have configured 96G memory for apache dirll, so can you
please advise how can we identify which SQL took a lot of memory? and how
can improve our performance?


Error Id: 40d789a6-91ee-4e0b-bfc9-a26358a43df3 on
theremin.root.digitalalchemy:31010]
org.apache.drill.common.exceptions.UserException: SYSTEM ERROR:
IllegalStateException: Memory was leaked by query. Memory leaked: (67043328)
Allocator(op:14:0:0:HashPartitionSender)
100/67043328/101535744/100 (res/actual/peak/limit)


Fragment 14:0

[Error Id: 40d789a6-91ee-4e0b-bfc9-a26358a43df3 on
theremin.root.digitalalchemy:31010]
   at
org.apache.drill.common.excep

[jira] [Created] (DRILL-6541) Upgrade ZooKeeper patch version to 3.4.11 for mapr profile

2018-06-26 Thread Bohdan Kazydub (JIRA)

Bohdan Kazydub created DRILL-6541:
-

 Summary: Upgrade ZooKeeper patch version to 3.4.11 for mapr profile
 Key: DRILL-6541
 URL: https://issues.apache.org/jira/browse/DRILL-6541
 Project: Apache Drill
  Issue Type: Task
Reporter: Bohdan Kazydub
Assignee: Bohdan Kazydub






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (DRILL-6540) Upgrade to HADOOP-3.1 libraries

2018-06-26 Thread Vitalii Diravka (JIRA)

Vitalii Diravka created DRILL-6540:
--

 Summary: Upgrade to HADOOP-3.1 libraries 
 Key: DRILL-6540
 URL: https://issues.apache.org/jira/browse/DRILL-6540
 Project: Apache Drill
  Issue Type: Improvement
Reporter: Vitalii Diravka


Currently Drill uses 2.7.1 version of hadoop libraries (hadoop-common, 
hadoop-hdfs, hadoop-annotations, hadoop-aws, hadoop-yarn-api, hadoop-client, 
hadoop-yarn-client).
Half of year ago the [Hadoop 
3.0|https://hadoop.apache.org/docs/r3.0.0/index.html] was released and recently 
it was an update - [Hadoop 3.1|https://hadoop.apache.org/docs/r3.1.0/]. 

To use Drill under Hadoop3.0 distribution we need this upgrade. Also the newer 
version includes new features, which can be useful for Drill.
This upgrade is also needed to leverage the newest version of zookeeper 
libraries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: Drill Hangout tomorrow 06/26

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: Apache drill show a lot of CLOSE_WAIT states when we access https://ip address:8047

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: Help with Apache Drill - S3 compatible storage connectivity

Re: Help with Apache Drill - S3 compatible storage connectivity

[jira] [Created] (DRILL-6543) Options for memory mgmt: Reserve allowance for non-buffered, and Hash-Join default to not fallback

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

[jira] [Created] (DRILL-6542) IndexOutOfBoundsException for multilevel lateral queries with schema changed partitioned complex data

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: Drill Hangout tomorrow 06/26

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

RE: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

Re: [ANNOUNCE] New PMC member: Vitalii Diravka

[ANNOUNCE] New PMC member: Vitalii Diravka

Re: Drill Hangout tomorrow 06/26

Apache drill show a lot of CLOSE_WAIT states when we access https://ip address:8047

[jira] [Created] (DRILL-6541) Upgrade ZooKeeper patch version to 3.4.11 for mapr profile

[jira] [Created] (DRILL-6540) Upgrade to HADOOP-3.1 libraries

30 matches

Site Navigation

Mail list logo

Footer information