Uploaded image for project: 'ORC'
  1. ORC
  2. ORC-203

Modify the StringStatistics to trim minimum and maximum values

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.6.0
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

        Issue Links

        causes

        Bug - A problem which impairs or prevents the functions of the product. ORC-422 Predicate push down can return incorrect value when lower/upper bounds are set

        • Major - Major loss of function.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. ORC-438 NPE in StringStatisticsImpl.merge()

        • Major - Major loss of function.
        • Closed

        Task - A task that needs to be done. ORC-440 Fix deserialization of the StringStatisticsImpl when truncated

        • Major - Major loss of function.
        • Closed
        links to

        Web Link GitHub Pull Request #169

        Web Link GitHub Pull Request #292

        Web Link GitHub Pull Request #299

          Activity
          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              smore Sandeep More
              Reporter:
              omalley Owen O'Malley

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment