[
https://issues.apache.org/jira/browse/DRILL-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527113#comment-16527113
]
ASF GitHub Bot commented on DRILL-6147:
---------------------------------------
vrozov commented on issue #1330: DRILL-6147: Adding Columnar Parquet Batch
Sizing functionality
URL: https://github.com/apache/drill/pull/1330#issuecomment-401234061
@sachouche I refer to your following comment:
>User should be able to control batch statistics behavior within a client
session: a) what operator stats to log and b) coarse vs fine grained stats
In any case, logging should be managed by a single entity (slf4j and
logback.xml). Having two different ways to manage logging is confusing and
error prone.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Limit batch size for Flat Parquet Reader
> ----------------------------------------
>
> Key: DRILL-6147
> URL: https://issues.apache.org/jira/browse/DRILL-6147
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Parquet
> Reporter: salim achouche
> Assignee: salim achouche
> Priority: Major
> Fix For: 1.14.0
>
>
> The Parquet reader currently uses a hard-coded batch size limit (32k rows)
> when creating scan batches; there is no parameter nor any logic for
> controlling the amount of memory used. This enhancement will allow Drill to
> take an extra input parameter to control direct memory usage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
