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

ANSI mode: runtime errors instead of returning null on invalid inputs

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.1.0
    • None
    • SQL
    • None

    Description

      We should respect the ANSI mode in more places. What we have done so far are mostly the overflow check in various operators. This ticket is to track a category of ANSI mode behaviors: operators should throw runtime errors instead of returning null when the input is invalid.

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            cloud_fan Wenchen Fan

            Dates

              Created:
              Updated:

              Slack

                Issue deployment