[
https://issues.apache.org/jira/browse/DRILL-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035932#comment-17035932
]
ASF GitHub Bot commented on DRILL-7578:
---------------------------------------
paul-rogers commented on issue #1978: DRILL-7578: HDF5 Metadata Queries Fail
with Large Files
URL: https://github.com/apache/drill/pull/1978#issuecomment-585561327
As it turns out, you'll get the same error if you try to do a normal query
on the data. So, we need a rule for what to do if a column is too large even at
runtime. You can fail the query (as now), you can truncate the data, you can
split the data into multiple rows.
Here is where it would be super-helpful if Drill supported normal SQL
warnings: then we could truncate the data when it is optional (as here), and
issue a warning. Sigh.
Working around a data size limitation is not a good use for a plugin config
option. The user would need a different config for each file.
Can you, instead, support some special column that is the preview? Don't
include the preview column in SELECT *. (I think there is an EVF trick for
that, I'll have to refresh my memory. I think I added it for one of your other
plugins.) If the user wants the preview, they can ask `SELECT name, preview
FROM ...`.
Otherwise, the error is correct: the data is too large for a Drill column.
----------------------------------------------------------------
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:
[email protected]
> 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)
