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

Fix default query timeout behavior for thin JDBC

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8
    • Component/s: sql
    • Labels:
      None
    • Ignite Flags:
      Docs Required, Release Notes Required

      Description

      After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver.
      Thin JDBC handles explicit query timeout on a client side. Default query timeout is tracked on a server side. As a server is not aware of explicit client timeout it is not possible to override a default timeout with longer explicit timeout (effectively a query will be cancelled after a default timeout expiration).

      The expected behavior is that an explicit query timeout always overrides a default one.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Pavlukhin Ivan Pavlukhin
                Reporter:
                Pavlukhin Ivan Pavlukhin
              • Votes:
                0 Vote for this issue
                Watchers:
                3 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 - 10m
                  10m