You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/02/11 17:10:00 UTC
[jira] [Commented] (DRILL-7578) HDF5 Metadata Queries Fail with
Large Files
[ https://issues.apache.org/jira/browse/DRILL-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034610#comment-17034610 ]
ASF GitHub Bot commented on DRILL-7578:
---------------------------------------
cgivre commented on pull request #1978: DRILL-7578: HDF5 Metadata Queries Fail with Large Files
URL: https://github.com/apache/drill/pull/1978
# [DRILL-7578](https://issues.apache.org/jira/browse/DRILL-7578): HDF5 Metadata Queries Fail with Large Files
## Description
HDF5 metadata queries were failing for files with large datasets. This PR adds a configuration option to avoid projecting the entire dataset in metadata queries and hence solves this issue.
## Documentation
Added this to the HDF5 documentation:
* `projectDatasetInMetadataQuery`: This causes the plugin to project the data set in metadata queries. Should be `false` for large files.
## Testing
Added new unit test to cover this configuration.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> HDF5 Metadata Queries Fail with Large Files
> -------------------------------------------
>
> Key: DRILL-7578
> URL: https://issues.apache.org/jira/browse/DRILL-7578
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.18.0
> Reporter: Charles Givre
> Assignee: Charles Givre
> Priority: Major
> Fix For: 1.18.0
>
>
> With large files, Drill runs out of memory when attempting to project large datasets in the metadata.
> This PR adds a configuration option which removes the dataset projection from metadata queries and fixes this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)