[
https://issues.apache.org/jira/browse/HIVE-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887727#comment-13887727
]
Lefty Leverenz commented on HIVE-5793:
--------------------------------------
[~thejas], your request isn't in the description yet and I'm not sure what you
meant:
{quote}
In the default.xml description, can you also state if
hive.fetch.task.conversion.threshold is set to less than 0, are the file
lengths going to be checked (I see that it doesn't.) ?
{quote}
The default value is -1, and the description says "Input threshold for applying
hive.fetch.task.conversion. If target table is native, input length is
calculated by summation of file lengths. If it's not native, storage handler
for the table can optionally implement
org.apache.hadoop.hive.ql.metadata.InputEstimator interface."
So does a negative value mean that file lengths are not calculated, therefore
fetch task conversion will always occur if hive.fetch.task.conversion is true?
Also, the threshold units aren't entirely obvious. Bytes? Apparently the
threshold is compared with a calculated or estimated input length, unless the
threshold is a negative number. But isn't that the same as a threshold of zero?
I can change the description in a new JIRA ticket, since I have other fixes to
make, but I need help figuring this out.
> Update hive-default.xml.template for HIVE-4002
> ----------------------------------------------
>
> Key: HIVE-5793
> URL: https://issues.apache.org/jira/browse/HIVE-5793
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
> Reporter: Navis
> Assignee: Navis
> Priority: Trivial
> Fix For: 0.13.0
>
> Attachments: HIVE-5793.1.patch.txt, HIVE-5793.2.patch.txt,
> HIVE-5793.3.patch.txt
>
>
> Addressing
> https://issues.apache.org/jira/browse/HIVE-3990?focusedCommentId=13818388&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13818388
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
