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

Jdbc Thin: implement client side best effort affinity

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.8
    • jdbc, sql

    Description

      Once partitions are extracted from original query (IGNITE-10305), it might be useful for thin clients: they could apply arguments locally and try to guess the best node where to send the request.

      Example: when there is only one partition, then it makes sense to send the request directly to that node, so that only one hop is needed.

      Attachments

        Issue Links

          is a child of

          New Feature - A new feature of the product, which has yet to be developed. IGNITE-11287 JDBC Thin: best effort affinity

          • Major - Major loss of function.
          • Resolved
          is blocked by

          Task - A task that needs to be done. IGNITE-10305 SQL: Optimize query execution if it targets only one or none partitions

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. IGNITE-11118 SQL: Ability to resolve argument without H2

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

          Web Link GitHub Pull Request #6358

          Activity

            People

              alapin Alexander Lapin
              vozerov Vladimir Ozerov
              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 - 0.5h
                  0.5h