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

Fix schema handling in deprecated "thin" driver.

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • sql
    • None

    Description

      Currently both drivers behave as follows: when schema is changed, it is converted to cache name automatically. This is wrong. We should do the following:
      1) Decouple schema name from cache name. Schema name should be separate field. No conversion.
      2) When JDBC driver is connected, schema is set to the schema target cache belongs to
      3) Cache name cannot be changed
      4) Cache name is always passed to all tasks as before
      5) Schema name is added to these tasks and propagated to respective SqlFieldsQuery.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. IGNITE-5320 Add well-known SQL schema where SQL caches will "live" by default

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

          Task - A task that needs to be done. IGNITE-5313 Get rid of H2Schema.cacheName

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              vozerov Vladimir Ozerov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: