[ 
https://issues.apache.org/jira/browse/ORC-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555951#comment-16555951
 ] 

ASF GitHub Bot commented on ORC-203:
------------------------------------

Github user omalley commented on a diff in the pull request:

    https://github.com/apache/orc/pull/292#discussion_r205180578
  
    --- Diff: java/core/src/java/org/apache/orc/impl/ColumnStatisticsImpl.java 
---
    @@ -543,35 +549,87 @@ public void reset() {
           super.reset();
           minimum = null;
           maximum = null;
    +      isLowerBoundSet = false;
    +      isUpperBoundSet = false;
           sum = 0;
         }
     
         @Override
         public void updateString(Text value) {
           if (minimum == null) {
    -        maximum = minimum = new Text(value);
    +        if(value.toString().length() > MAX_STRING_LENGTH_RECORDED) {
    +         minimum = new Text(
    --- End diff --
    
    Let's make a corresponding truncateLowerBound so that we can have one place 
to change.


> 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: Sandeep More
>            Priority: Major
>
> 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
(v7.6.3#76005)

Reply via email to