BI Tool Demo on Drill

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, Charles Givre has been working tediously at finding existing tools that bring the

[GitHub] cgivre commented on a change in pull request #1530: DRILL-6582: SYSLOG (RFC-5424) Format Plugin

cgivre commented on a change in pull request #1530: DRILL-6582: SYSLOG (RFC-5424) Format Plugin URL: https://github.com/apache/drill/pull/1530#discussion_r254140727 ## File path: protocol/src/main/java/org/apache/drill/exec/proto/UserBitShared.java ## @@ -895,6 +903,7 @@

[GitHub] cgivre commented on a change in pull request #1530: DRILL-6582: SYSLOG (RFC-5424) Format Plugin

cgivre commented on a change in pull request #1530: DRILL-6582: SYSLOG (RFC-5424) Format Plugin URL: https://github.com/apache/drill/pull/1530#discussion_r254140158 ## File path: contrib/format-syslog/src/main/resources/checkstyle-config.xml ## @@ -0,0 +1,40 @@ + + +http:/

Re: Performance issue when query from web console.

Hi Nai, First of all, Drill is up to version 1.15. There have been SIGNIFICANT improvements in Drill’s performance since v 1.4 and I would strongly recommend you upgrade to the most current version before you start trying to debug. Best, — C > On Feb 10, 2019, at 20:37, Nai Yan. wrote: > >

Performance issue when query from web console.

Greetings, When we are trying Drill, we have encountered performance issue when query from web console. From backend, the resultset already returned (to foreman), however, it will take unreasonable time (in general need to take 5 ~ 10 seconds more) to display on the web. We are using Dri

[GitHub] vvysotskyi opened a new pull request #1638: DRILL-7022: Partition pruning is not happening the first time after the metadata auto-refresh

vvysotskyi opened a new pull request #1638: DRILL-7022: Partition pruning is not happening the first time after the metadata auto-refresh URL: https://github.com/apache/drill/pull/1638 For problem description please see [DRILL-7022](https://issues.apache.org/jira/browse/DRILL-7022). -

[GitHub] jcmcote commented on issue #1612: DRILL-6970: fix issue with logregex format plugin where drillbuf was overflowing

jcmcote commented on issue #1612: DRILL-6970: fix issue with logregex format plugin where drillbuf was overflowing URL: https://github.com/apache/drill/pull/1612#issuecomment-462157816 I did not have time to add a test case yet. However I know the fix is good, using it in production.

[GitHub] cgivre commented on issue #1637: DRILL-7032: Ignore corrupt rows in a PCAP file

cgivre commented on issue #1637: DRILL-7032: Ignore corrupt rows in a PCAP file URL: https://github.com/apache/drill/pull/1637#issuecomment-462151344 Actually, some good news here… I ran some test queries on the corrupted file and it seemed to work pretty well. I didn’t get any except

[GitHub] cgivre commented on issue #1637: DRILL-7032: Ignore corrupt rows in a PCAP file

cgivre commented on issue #1637: DRILL-7032: Ignore corrupt rows in a PCAP file URL: https://github.com/apache/drill/pull/1637#issuecomment-462139674 Thanks Bob! I’d really like to try this out with other corrupted PCAP files to see if it works properly. — C > On Feb 10, 201

[GitHub] hrbrmstr commented on a change in pull request #1637: DRILL-7032: Ignore corrupt rows in a PCAP file

hrbrmstr commented on a change in pull request #1637: DRILL-7032: Ignore corrupt rows in a PCAP file URL: https://github.com/apache/drill/pull/1637#discussion_r255340198 ## File path: exec/java-exec/src/main/java/org/apache/drill/exec/store/pcap/decoder/Packet.java ## @@