[jira] [Commented] (DRILL-5379) Set Hdfs Block Size based on Parquet Block Size

[ https://issues.apache.org/jira/browse/DRILL-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1606#comment-1606 ] ASF GitHub Bot commented on DRILL-5379: --- Github user ppadma commented on the issue:

[jira] [Commented] (DRILL-5518) Roll-up of a number of test framework enhancements

[ https://issues.apache.org/jira/browse/DRILL-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067659#comment-16067659 ] ASF GitHub Bot commented on DRILL-5518: --- Github user amansinha100 commented on the issue:

[jira] [Comment Edited] (DRILL-5256) Exception in thread "main" java.lang.ExceptionInInitializerError

[ https://issues.apache.org/jira/browse/DRILL-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061413#comment-16061413 ] N Campbell edited comment on DRILL-5256 at 6/29/17 3:00 AM: The Apache JDBC

[jira] [Updated] (DRILL-5617) Spill file name collisions when spill file is on a shared file system

[ https://issues.apache.org/jira/browse/DRILL-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5617: --- Summary: Spill file name collisions when spill file is on a shared file system (was: spill filename

[jira] [Assigned] (DRILL-5617) spill filename conflict

[ https://issues.apache.org/jira/browse/DRILL-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned DRILL-5617: -- Assignee: Paul Rogers (was: Boaz Ben-Zvi) > spill filename conflict > ---

[jira] [Comment Edited] (DRILL-5453) Managed External Sort : Sorting on a lot of columns is taking unreasonably long time

[ https://issues.apache.org/jira/browse/DRILL-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067605#comment-16067605 ] Paul Rogers edited comment on DRILL-5453 at 6/29/17 2:37 AM: - This bug is a

[jira] [Issue Comment Deleted] (DRILL-5453) Managed External Sort : Sorting on a lot of columns is taking unreasonably long time

[ https://issues.apache.org/jira/browse/DRILL-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5453: --- Comment: was deleted (was: Will be resolved by controlling batch size, which is being done by the

[jira] [Assigned] (DRILL-5453) Managed External Sort : Sorting on a lot of columns is taking unreasonably long time

[ https://issues.apache.org/jira/browse/DRILL-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned DRILL-5453: -- Assignee: Paul Rogers > Managed External Sort : Sorting on a lot of columns is taking

[jira] [Commented] (DRILL-5453) Managed External Sort : Sorting on a lot of columns is taking unreasonably long time

[ https://issues.apache.org/jira/browse/DRILL-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067607#comment-16067607 ] Paul Rogers commented on DRILL-5453: Will be resolved by controlling batch size, which is being done

[jira] [Commented] (DRILL-5453) Managed External Sort : Sorting on a lot of columns is taking unreasonably long time

[ https://issues.apache.org/jira/browse/DRILL-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067606#comment-16067606 ] Paul Rogers commented on DRILL-5453: Will be resolved by controlling batch size, which is being done

[jira] [Commented] (DRILL-5453) Managed External Sort : Sorting on a lot of columns is taking unreasonably long time

[ https://issues.apache.org/jira/browse/DRILL-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067605#comment-16067605 ] Paul Rogers commented on DRILL-5453: This bug is a tough one. There is certainly a bug, but it is not

[jira] [Commented] (DRILL-5379) Set Hdfs Block Size based on Parquet Block Size

[ https://issues.apache.org/jira/browse/DRILL-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067554#comment-16067554 ] ASF GitHub Bot commented on DRILL-5379: --- Github user kkhatua commented on the issue:

[jira] [Commented] (DRILL-5420) all cores at 100% of all servers

[ https://issues.apache.org/jira/browse/DRILL-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067510#comment-16067510 ] ASF GitHub Bot commented on DRILL-5420: --- Github user kkhatua commented on a diff in the pull

[jira] [Commented] (DRILL-5432) Want a memory format for PCAP files

[ https://issues.apache.org/jira/browse/DRILL-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067459#comment-16067459 ] ASF GitHub Bot commented on DRILL-5432: --- Github user paul-rogers commented on the issue:

[jira] [Created] (DRILL-5618) Allow non-core storage plugins to define an initial configuration

Paul Rogers created DRILL-5618: -- Summary: Allow non-core storage plugins to define an initial configuration Key: DRILL-5618 URL: https://issues.apache.org/jira/browse/DRILL-5618 Project: Apache Drill

[jira] [Created] (DRILL-5617) spill filename conflict

Chun Chang created DRILL-5617: - Summary: spill filename conflict Key: DRILL-5617 URL: https://issues.apache.org/jira/browse/DRILL-5617 Project: Apache Drill Issue Type: Bug Components:

[jira] [Commented] (DRILL-5154) OOM error in external sort on top of 400GB data set generated using terasort benchamark

[ https://issues.apache.org/jira/browse/DRILL-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067438#comment-16067438 ] Paul Rogers commented on DRILL-5154: [~rkins], this data set is too large to verify on my development

[jira] [Assigned] (DRILL-5154) OOM error in external sort on top of 400GB data set generated using terasort benchamark

[ https://issues.apache.org/jira/browse/DRILL-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned DRILL-5154: -- Assignee: Paul Rogers > OOM error in external sort on top of 400GB data set generated using

[jira] [Commented] (DRILL-5146) Unnecessary spilling to disk by sort when we only have 5000 rows with one column

[ https://issues.apache.org/jira/browse/DRILL-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067434#comment-16067434 ] Paul Rogers commented on DRILL-5146: This case works with the code in DRILL-5601. {code} Results:

[jira] [Commented] (DRILL-5616) Hash Agg Spill: OOM while reading irregular varchar data

[ https://issues.apache.org/jira/browse/DRILL-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067409#comment-16067409 ] Boaz Ben-Zvi commented on DRILL-5616: - Here is what likely caused the OOM – an internal doubling of

[jira] [Commented] (DRILL-5616) Hash Agg Spill: OOM while reading irregular varchar data

[ https://issues.apache.org/jira/browse/DRILL-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067410#comment-16067410 ] Boaz Ben-Zvi commented on DRILL-5616: - Another possible solution: Increase the frequency of memory

[jira] [Commented] (DRILL-5616) Hash Agg Spill: OOM while reading irregular varchar data

[ https://issues.apache.org/jira/browse/DRILL-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067407#comment-16067407 ] Boaz Ben-Zvi commented on DRILL-5616: - More detail about the above failure: {code} Unable to allocate

[jira] [Updated] (DRILL-5616) Hash Agg Spill: OOM while reading irregular varchar data

[ https://issues.apache.org/jira/browse/DRILL-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boaz Ben-Zvi updated DRILL-5616: Description: An OOM while aggregating a table of two varchar columns where sizes vary

[jira] [Created] (DRILL-5616) Hash Agg Spill: OOM while reading irregular varchar data

Boaz Ben-Zvi created DRILL-5616: --- Summary: Hash Agg Spill: OOM while reading irregular varchar data Key: DRILL-5616 URL: https://issues.apache.org/jira/browse/DRILL-5616 Project: Apache Drill

[jira] [Commented] (DRILL-5416) Vectors read from disk report incorrect memory sizes

[ https://issues.apache.org/jira/browse/DRILL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067303#comment-16067303 ] Paul Rogers commented on DRILL-5416: A major portion of the changes in DRILL-5601 address this issue

[jira] [Assigned] (DRILL-5416) Vectors read from disk report incorrect memory sizes

[ https://issues.apache.org/jira/browse/DRILL-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned DRILL-5416: -- Assignee: Paul Rogers > Vectors read from disk report incorrect memory sizes >

[jira] [Commented] (DRILL-5443) Managed External Sort fails with OOM while spilling to disk

[ https://issues.apache.org/jira/browse/DRILL-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067298#comment-16067298 ] Paul Rogers commented on DRILL-5443: Query runs, on the Mac, using the fixes from DRILL-5601. {code}

[jira] [Commented] (DRILL-5420) all cores at 100% of all servers

[ https://issues.apache.org/jira/browse/DRILL-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067247#comment-16067247 ] ASF GitHub Bot commented on DRILL-5420: --- Github user parthchandra commented on a diff in the pull

[jira] [Commented] (DRILL-5253) External sort fails with OOM error (Fails to allocate sv2)

[ https://issues.apache.org/jira/browse/DRILL-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067203#comment-16067203 ] Rahul Challapalli commented on DRILL-5253: -- Please ignore the above comment. The error happened

[jira] [Commented] (DRILL-5447) Managed External Sort : Unable to allocate sv2 vector

[ https://issues.apache.org/jira/browse/DRILL-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067180#comment-16067180 ] Paul Rogers commented on DRILL-5447: This test passes, on the Mac, using the fixes from DRILL-5601:

[jira] [Comment Edited] (DRILL-5253) External sort fails with OOM error (Fails to allocate sv2)

[ https://issues.apache.org/jira/browse/DRILL-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067136#comment-16067136 ] Rahul Challapalli edited comment on DRILL-5253 at 6/28/17 8:23 PM: --- One

[jira] [Comment Edited] (DRILL-5253) External sort fails with OOM error (Fails to allocate sv2)

[ https://issues.apache.org/jira/browse/DRILL-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067136#comment-16067136 ] Rahul Challapalli edited comment on DRILL-5253 at 6/28/17 8:20 PM: --- One

[jira] [Commented] (DRILL-5253) External sort fails with OOM error (Fails to allocate sv2)

[ https://issues.apache.org/jira/browse/DRILL-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067136#comment-16067136 ] Rahul Challapalli commented on DRILL-5253: -- One more scenario where I hit this error on a single

[jira] [Commented] (DRILL-4282) Allow to customize address registered in zookeeper

[ https://issues.apache.org/jira/browse/DRILL-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067041#comment-16067041 ] Kunal Khatua commented on DRILL-4282: - @johnnywalee Can you provide some more detail? I don't see any

[jira] [Updated] (DRILL-3640) Drill JDBC driver support Statement.setQueryTimeout(int)

[ https://issues.apache.org/jira/browse/DRILL-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua updated DRILL-3640: Reviewer: Laurent Goujon > Drill JDBC driver support Statement.setQueryTimeout(int) >

[jira] [Updated] (DRILL-5379) Set Hdfs Block Size based on Parquet Block Size

[ https://issues.apache.org/jira/browse/DRILL-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua updated DRILL-5379: Reviewer: Khurram Faraaz [~khfaraaz] Can you add tests for this and close the JIRA after that? >

[jira] [Commented] (DRILL-5420) all cores at 100% of all servers

[ https://issues.apache.org/jira/browse/DRILL-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066956#comment-16066956 ] ASF GitHub Bot commented on DRILL-5420: --- Github user kkhatua commented on the issue:

[jira] [Commented] (DRILL-5435) Using Limit causes Memory Leaked Error since 1.10

[ https://issues.apache.org/jira/browse/DRILL-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066953#comment-16066953 ] Kunal Khatua commented on DRILL-5435: - [~fmethot] / [~andreatbonanno] there is a PR for DRILL-5420

[jira] [Updated] (DRILL-5420) all cores at 100% of all servers

[ https://issues.apache.org/jira/browse/DRILL-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua updated DRILL-5420: Reviewer: Parth Chandra > all cores at 100% of all servers > > >

[jira] [Commented] (DRILL-5420) all cores at 100% of all servers

[ https://issues.apache.org/jira/browse/DRILL-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066939#comment-16066939 ] ASF GitHub Bot commented on DRILL-5420: --- GitHub user kkhatua opened a pull request:

[jira] [Commented] (DRILL-5420) all cores at 100% of all servers

[ https://issues.apache.org/jira/browse/DRILL-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066933#comment-16066933 ] Kunal Khatua commented on DRILL-5420: - The CPU churn is most easily reproduced by cancellation of a

[jira] [Assigned] (DRILL-5420) all cores at 100% of all servers

[ https://issues.apache.org/jira/browse/DRILL-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua reassigned DRILL-5420: --- Assignee: Kunal Khatua (was: Parth Chandra) > all cores at 100% of all servers >

[jira] [Commented] (DRILL-3993) Rebase Drill on Calcite master branch

[ https://issues.apache.org/jira/browse/DRILL-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066793#comment-16066793 ] Muhammad Gelbana commented on DRILL-3993: - I believe we need to change that and target whatever

[jira] [Created] (DRILL-5615) DatabaseMetadata.getColumns fails with SQL Serrver (Unknown SQL type -155)

N Campbell created DRILL-5615: - Summary: DatabaseMetadata.getColumns fails with SQL Serrver (Unknown SQL type -155) Key: DRILL-5615 URL: https://issues.apache.org/jira/browse/DRILL-5615 Project: Apache

[jira] [Created] (DRILL-5614) DatabaseMetadata.getColumns fails with ORACLE (Unknown SQL type 101)

N Campbell created DRILL-5614: - Summary: DatabaseMetadata.getColumns fails with ORACLE (Unknown SQL type 101) Key: DRILL-5614 URL: https://issues.apache.org/jira/browse/DRILL-5614 Project: Apache Drill

[jira] [Updated] (DRILL-5613) DatabaseMetadata.getTables throws exception when null used for catalog/schema or % used for schema

[ https://issues.apache.org/jira/browse/DRILL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated DRILL-5613: -- Description: DatabaseMetadata.getTables supports being passed a NULL value for a catalog/schema and %

[jira] [Updated] (DRILL-5613) DatabaseMetadata.getTables throws exception when null used for catalog/schema or % used for schema

[ https://issues.apache.org/jira/browse/DRILL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated DRILL-5613: -- Description: DatabaseMetadata.getTables supports being passed a NULL value for a catalog/schema and %

[jira] [Updated] (DRILL-5613) DatabaseMetadata.getTables throws exception is the catalog or schema parameter is set to NULL

[ https://issues.apache.org/jira/browse/DRILL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated DRILL-5613: -- Summary: DatabaseMetadata.getTables throws exception is the catalog or schema parameter is set to NULL

[jira] [Updated] (DRILL-5613) DatabaseMetadata.getTables throws exception is the catalog or schema parameter is set to NULL

[ https://issues.apache.org/jira/browse/DRILL-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated DRILL-5613: -- Description: DatabaseMetadata.getTables supports being passed a NULL value for a catalog

[jira] [Created] (DRILL-5613) DatabaseMetadata.getTables throws exception is the catalog parameter is set to NULL

N Campbell created DRILL-5613: - Summary: DatabaseMetadata.getTables throws exception is the catalog parameter is set to NULL Key: DRILL-5613 URL: https://issues.apache.org/jira/browse/DRILL-5613 Project: