Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.4.0
    • Component/s: core, OpenShift
    • Labels:
      None
    • Sprint:
      DV Sprint 58, DV Sprint 59
    • Story Points:
      2

      Description

      Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well.

      Things break down roughly into:

      • Single-pod support
        • Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now?
        • validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436
      • Multi-pod support
        • everything from single-pod support
        • Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication.
        • requires replacing the logic that detect failed materialization loads
        • internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required)

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  shawkins Steven Hawkins
                  Reporter:
                  shawkins Steven Hawkins
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 1 day, 7 hours Original Estimate - 1 day, 7 hours
                    1d 7h
                    Remaining:
                    Time Spent - 2 days, 3 hours Remaining Estimate - 2 hours
                    2h
                    Logged:
                    Time Spent - 2 days, 3 hours Remaining Estimate - 2 hours
                    2d 3h