Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-5876

MongoDB import name conflict issues

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 14.0
    • None
    • Misc. Connectors
    • None
    • DV Sprint 60
    • 0.5

      There are two issues with the import logic and naming:

      1. There's an assumption that any table in the schema was created by the mongodb import. In general this is not true as other imports or ddl may have already run.
      2. If a child construct has a field name that matches an existing table, the two entities will get intertwined in the metadata, which is invalid.

              rhn-engineering-shawkins Steven Hawkins
              rhn-engineering-shawkins Steven Hawkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Time Spent - 3 hours, 30 minutes Remaining Estimate - 30 minutes
                  30m
                  Logged:
                  Time Spent - 3 hours, 30 minutes Remaining Estimate - 30 minutes
                  3h 30m