[jira] [Updated] (DRILL-6853) Parquet Complex Reader for nested schema should have configurable memory or max records to fetch

2019-01-07 Thread Bridget Bevens (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bridget Bevens updated DRILL-6853:
--
Labels: doc-complete pull-request-available ready-to-commit  (was: 
doc-impacting pull-request-available ready-to-commit)

> Parquet Complex Reader for nested schema should have configurable memory or 
> max records to fetch
> 
>
> Key: DRILL-6853
> URL: https://issues.apache.org/jira/browse/DRILL-6853
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Nitin Sharma
>Assignee: salim achouche
>Priority: Major
>  Labels: doc-complete, pull-request-available, ready-to-commit
> Fix For: 1.15.0
>
>
> Parquet Complex reader while fetching nested schema should have configurable 
> memory or max records to fetch and not default to 4000 records.
> While scanning TB of data with wider columns, this could easily cause OOM 
> issues. 



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


[jira] [Updated] (DRILL-6853) Parquet Complex Reader for nested schema should have configurable memory or max records to fetch

2018-11-15 Thread Kunal Khatua (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kunal Khatua updated DRILL-6853:

Labels: doc-impacting pull-request-available ready-to-commit  (was: 
pull-request-available ready-to-commit)

> Parquet Complex Reader for nested schema should have configurable memory or 
> max records to fetch
> 
>
> Key: DRILL-6853
> URL: https://issues.apache.org/jira/browse/DRILL-6853
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Nitin Sharma
>Assignee: salim achouche
>Priority: Major
>  Labels: doc-impacting, pull-request-available, ready-to-commit
> Fix For: 1.15.0
>
>
> Parquet Complex reader while fetching nested schema should have configurable 
> memory or max records to fetch and not default to 4000 records.
> While scanning TB of data with wider columns, this could easily cause OOM 
> issues. 



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


[jira] [Updated] (DRILL-6853) Parquet Complex Reader for nested schema should have configurable memory or max records to fetch

2018-11-15 Thread Timothy Farkas (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Farkas updated DRILL-6853:
--
Labels: pull-request-available ready-to-commit  (was: 
pull-request-available)

> Parquet Complex Reader for nested schema should have configurable memory or 
> max records to fetch
> 
>
> Key: DRILL-6853
> URL: https://issues.apache.org/jira/browse/DRILL-6853
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Nitin Sharma
>Assignee: salim achouche
>Priority: Major
>  Labels: pull-request-available, ready-to-commit
> Fix For: 1.15.0
>
>
> Parquet Complex reader while fetching nested schema should have configurable 
> memory or max records to fetch and not default to 4000 records.
> While scanning TB of data with wider columns, this could easily cause OOM 
> issues. 



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


[jira] [Updated] (DRILL-6853) Parquet Complex Reader for nested schema should have configurable memory or max records to fetch

2018-11-15 Thread salim achouche (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

salim achouche updated DRILL-6853:
--
Labels: pull-request-available  (was: )

> Parquet Complex Reader for nested schema should have configurable memory or 
> max records to fetch
> 
>
> Key: DRILL-6853
> URL: https://issues.apache.org/jira/browse/DRILL-6853
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Nitin Sharma
>Assignee: salim achouche
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Parquet Complex reader while fetching nested schema should have configurable 
> memory or max records to fetch and not default to 4000 records.
> While scanning TB of data with wider columns, this could easily cause OOM 
> issues. 



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


[jira] [Updated] (DRILL-6853) Parquet Complex Reader for nested schema should have configurable memory or max records to fetch

2018-11-15 Thread salim achouche (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

salim achouche updated DRILL-6853:
--
 Reviewer: Timothy Farkas
Fix Version/s: 1.15.0

> Parquet Complex Reader for nested schema should have configurable memory or 
> max records to fetch
> 
>
> Key: DRILL-6853
> URL: https://issues.apache.org/jira/browse/DRILL-6853
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Nitin Sharma
>Assignee: salim achouche
>Priority: Major
> Fix For: 1.15.0
>
>
> Parquet Complex reader while fetching nested schema should have configurable 
> memory or max records to fetch and not default to 4000 records.
> While scanning TB of data with wider columns, this could easily cause OOM 
> issues. 



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


[jira] [Updated] (DRILL-6853) Parquet Complex Reader for nested schema should have configurable memory or max records to fetch

2018-11-14 Thread Nitin Sharma (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Sharma updated DRILL-6853:

Affects Version/s: 1.14.0

> Parquet Complex Reader for nested schema should have configurable memory or 
> max records to fetch
> 
>
> Key: DRILL-6853
> URL: https://issues.apache.org/jira/browse/DRILL-6853
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Nitin Sharma
>Priority: Major
>
> Parquet Complex reader while fetching nested schema should have configurable 
> memory or max records to fetch and not default to 4000 records.
> While scanning TB of data with wider columns, this could easily cause OOM 
> issues. 



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