[jira] [Created] (DRILL-7037) Apache Drill Crashes when a 50mb json string is queried via the REST API provided

2019-02-11 Thread Ayush Sharma (JIRA)
Ayush Sharma created DRILL-7037: --- Summary: Apache Drill Crashes when a 50mb json string is queried via the REST API provided Key: DRILL-7037 URL: https://issues.apache.org/jira/browse/DRILL-7037

[jira] [Created] (DRILL-7036) Improve UI for alert and error messages

2019-02-11 Thread Kunal Khatua (JIRA)
Kunal Khatua created DRILL-7036: --- Summary: Improve UI for alert and error messages Key: DRILL-7036 URL: https://issues.apache.org/jira/browse/DRILL-7036 Project: Apache Drill Issue Type:

Re: Re: Performance issue when query from web console.

2019-02-11 Thread Kunal Khatua
1.16 is slated to come out in a couple of months. But if the feature makes it in sooner, you can always build Drill from the master branch if you cnanot wait until the release. ~ Kunal On 2/11/2019 5:32:55 PM, Nai Yan. wrote: Thank you for you information. That's great. Hope for v 1.16. By the

Re: Re: Performance issue when query from web console.

2019-02-11 Thread Nai Yan.
Thank you for you information. That's great. Hope for v 1.16. By the way, when will it come out? Nai Yan From: Kunal Khatua Date: 2019-02-12 01:56 To: dev@drill.apache.org Subject: Re: Performance issue when query from web console. Hi Nai Yan The issue you are seeing is because when

Re: Slack workspace for Drill discussions

2019-02-11 Thread Abhishek Girish
I found a way to create an invite link which is open to all and never expires. Once we decide on the workspace, we can probably add it to

Re: Slack workspace for Drill discussions

2019-02-11 Thread Charles Givre
Sent from my iPhone > On Feb 11, 2019, at 18:30, Abhishek Girish wrote: > > Hey folks, > > There have been some questions on a Slack workspace for Drill - it's > popular for multiple open source projects and I think we should encourage > active participation as well. The previous

Re: BI Tool Demo on Drill

2019-02-11 Thread Veera Naranammalpuram
+1 On Mon, Feb 11, 2019 at 5:55 PM Gautam Parai wrote: > +1 > > On Mon, Feb 11, 2019 at 2:54 PM Hanumanth Maduri > wrote: > > > +1 > > > > > On Feb 11, 2019, at 2:50 PM, Aman Sinha wrote: > > > > > > +1 > > > > > >> On Mon, Feb 11, 2019 at 12:08 PM Abhishek Ravi > > wrote: > > >> > > >> +1

Slack workspace for Drill discussions

2019-02-11 Thread Abhishek Girish
Hey folks, There have been some questions on a Slack workspace for Drill - it's popular for multiple open source projects and I think we should encourage active participation as well. The previous Slack workspace for Apache Drill has been idle for ~3 years and we've been unable to invite new

Re: BI Tool Demo on Drill

2019-02-11 Thread Gautam Parai
+1 On Mon, Feb 11, 2019 at 2:54 PM Hanumanth Maduri wrote: > +1 > > > On Feb 11, 2019, at 2:50 PM, Aman Sinha wrote: > > > > +1 > > > >> On Mon, Feb 11, 2019 at 12:08 PM Abhishek Ravi > wrote: > >> > >> +1 > >> > >>> On Mon, Feb 11, 2019 at 11:54 AM Pritesh Maker > wrote: > >>> > >>> +1 >

Re: BI Tool Demo on Drill

2019-02-11 Thread Aman Sinha
+1 On Mon, Feb 11, 2019 at 12:08 PM Abhishek Ravi wrote: > +1 > > On Mon, Feb 11, 2019 at 11:54 AM Pritesh Maker wrote: > > > +1 > > > > On Mon, Feb 11, 2019 at 4:40 AM Charles Givre wrote: > > > > > +1 ;-) > > > > > > > > > > On Feb 11, 2019, at 02:02, Kunal Khatua wrote: > > > > > > > > Hi

Re: BI Tool Demo on Drill

2019-02-11 Thread Abhishek Ravi
+1 On Mon, Feb 11, 2019 at 11:54 AM Pritesh Maker wrote: > +1 > > On Mon, Feb 11, 2019 at 4:40 AM Charles Givre wrote: > > > +1 ;-) > > > > > > > On Feb 11, 2019, at 02:02, Kunal Khatua wrote: > > > > > > Hi guys > > > > > > We often use the hangouts to discuss about issues or some integral >

Re: BI Tool Demo on Drill

2019-02-11 Thread Pritesh Maker
+1 On Mon, Feb 11, 2019 at 4:40 AM Charles Givre wrote: > +1 ;-) > > > > On Feb 11, 2019, at 02:02, Kunal Khatua wrote: > > > > Hi guys > > > > We often use the hangouts to discuss about issues or some integral > framework related feature to improve Drill. However, we've probably never >

[jira] [Created] (DRILL-7035) Drill C++ Client crashes on multiple SaslAuthenticatorImpl Destruction due to communication error

2019-02-11 Thread Rob Wu (JIRA)
Rob Wu created DRILL-7035: - Summary: Drill C++ Client crashes on multiple SaslAuthenticatorImpl Destruction due to communication error Key: DRILL-7035 URL: https://issues.apache.org/jira/browse/DRILL-7035

Re: Travis CI improvements

2019-02-11 Thread Kunal Khatua
Thanks for the clarification, Vova ! With the Maven (M2) cache, if your numbers have dropped that low.. it should be fine. I was concerned because TravisCI gets kicked off almost instantaneously when a commit gets pushed to my private repo, and I didn't want to increase the burden on the CI

[GitHub] vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version

2019-02-11 Thread GitBox
vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version URL: https://github.com/apache/drill/pull/1639#discussion_r255524667 ## File path: exec/java-exec/src/main/java/org/apache/drill/exec/util/ProtobufPatcher.java ## @@ -0,0

[GitHub] vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version

2019-02-11 Thread GitBox
vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version URL: https://github.com/apache/drill/pull/1639#discussion_r255515963 ## File path: contrib/storage-hbase/src/main/java/com/google/protobuf/LiteralByteString.java ## @@

[GitHub] vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version

2019-02-11 Thread GitBox
vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version URL: https://github.com/apache/drill/pull/1639#discussion_r255517720 ## File path: exec/java-exec/src/main/java/org/apache/drill/exec/util/ProtobufPatcher.java ## @@ -0,0

[GitHub] vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version

2019-02-11 Thread GitBox
vvysotskyi commented on a change in pull request #1639: DRILL-6642: Update protocol-buffers version URL: https://github.com/apache/drill/pull/1639#discussion_r255516819 ## File path: exec/java-exec/src/main/java/org/apache/drill/exec/util/ProtobufPatcher.java ## @@ -0,0

Re: Performance issue when query from web console.

2019-02-11 Thread Charles Givre
I would definitely recommend updating to the latest version. — C > On Feb 11, 2019, at 09:48, Nai Yan. wrote: > > Thanks, Charles. > If there's any SIGNIFICANT improvement since v 1.14 (versus v 1.15)? I have > been thinking it's a configuration issue. > > Thanks again! > > > > Nai Yan

Re: Re: Performance issue when query from web console.

2019-02-11 Thread Nai Yan.
Thanks, Charles. If there's any SIGNIFICANT improvement since v 1.14 (versus v 1.15)? I have been thinking it's a configuration issue. Thanks again! Nai Yan From: Charles Givre Date: 2019-02-11 10:21 To: dev Subject: Re: Performance issue when query from web console. Hi Nai, First of

Re: BI Tool Demo on Drill

2019-02-11 Thread Charles Givre
+1 ;-) > On Feb 11, 2019, at 02:02, Kunal Khatua wrote: > > Hi guys > > We often use the hangouts to discuss about issues or some integral framework > related feature to improve Drill. However, we've probably never really had > one regarding user experience specifically. > > However,

[GitHub] agozhiy opened a new pull request #1639: DRILL-6642: Update protocol-buffers version

2019-02-11 Thread GitBox
agozhiy opened a new pull request #1639: DRILL-6642: Update protocol-buffers version URL: https://github.com/apache/drill/pull/1639 1. Updated protobuf to version 3.6.0 2. Added protobuf to the root pom dependency management 3. Added classes BoundedByteString and LiteralByteString

Re: Travis CI improvements

2019-02-11 Thread Vova Vysotskyi
Thanks for the proposal, but I think enabling build only when changes in .proto files wouldn't help, since changes may be accidentally done in the corresponding java or c++ classes. Adding check for changes in the specific list of java/c++ files also may not help, since in future may be added new