Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-19539

Introduce exception handler to prevent leaking internal exceptions to the end user

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0
    • None

    Description

      It seems reasonable to introduce some kind of mapper/handler of internal exceptions in order to prevent leaking internal exceptions to the end user.
      All public methods/interfaces should only throw IgniteException/IgniteCheckedException instances and their subclasses.
      All internal exceptions should be mapped to IgniteException with the INTERNAL_ERR error code and be considered as a bug.

      Attachments

        Issue Links

          Activity

            People

              slava.koptilin Vyacheslav Koptilin
              slava.koptilin Vyacheslav Koptilin
              Ivan Bessonov Ivan Bessonov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4.5h
                  4.5h