Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-10095

Should not use the private field of BigInteger

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete CommentsDelete
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.5.0
    • 1.5.0
    • SQL
    • None

    Description

      In UnsafeRow, we use the private field of BigInteger for better performance, but it actually didn't contribute much to end-to-end runtime, and make it not portable (may fail on other JVM implementations).

      So we should use the public API instead.

      Attachments

        Issue Links

        relates to

        Improvement - An improvement or enhancement to an existing feature or task. SPARK-9644 Support update DecimalType with precision > 18 in UnsafeRow

        • Critical - Crashes, loss of data, severe memory leak.
        • Resolved
        links to

        Pull request #8286 [Github] Pull Request #8286 (davies)

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            davies Davies Liu Assign to me
            davies Davies Liu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment