Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. TEIIDDES-2460

JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.3, 9.2
    • None
    • Import/Export
    • None
    • Hide

      Steps to Reproduce:
      1. Create loopback VDB, add table DATA with two columns, one of type integer and one of the string
      2. Deploy the loopback VDB
      3. Reuse the looback VDB
      3.1. Import the loopback VDB through JDBC importer
      "Import as VDB source model" have to be checked
      3.2 Select schema with created in step 1.

      Show
      Steps to Reproduce: 1. Create loopback VDB, add table DATA with two columns, one of type integer and one of the string 2. Deploy the loopback VDB 3. Reuse the looback VDB 3.1. Import the loopback VDB through JDBC importer "Import as VDB source model" have to be checked 3.2 Select schema with created in step 1.

    Description

      When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised

      Version-Release number of selected component (if applicable):

      Actual results:
      Imported schema has changed integer data type to biginteger data type.

      Expected results:
      Imported schema will be identical to original schema.

      Additional info:
      Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. TEIIDDES-2554 Import of REST service with columns set to 'integer' type results in "Expected biginteger, but was integer."

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              blafond Barry LaFond
              blafond Barry LaFond
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: