[
https://issues.apache.org/jira/browse/ORC-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177274#comment-16177274
]
ASF GitHub Bot commented on ORC-203:
------------------------------------
Github user xndai commented on the issue:
https://github.com/apache/orc/pull/169
@dain if the concern is the performance, should we also limit the string
length when generate stats in writer path, which in my opinion is more costly?
I think if we keep the string compare up to 1024 bytes, we won't need to trim
at the end.
> Modify the StringStatistics to trim minimum and maximum values
> --------------------------------------------------------------
>
> Key: ORC-203
> URL: https://issues.apache.org/jira/browse/ORC-203
> Project: ORC
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Ajay Yadava
>
> Currently the StringStatistics will record the entire value for minimum or
> maximum. It creates large protobuf objects and serves very little value. I
> think we should trim long strings to 1024 characters and record the fact that
> they were trimmed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
