Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-2039

FY18 Revisit Design of L3 Support in Qserv

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Invalid
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:
      None
    • Epic Name:
      FY18 L3 Support in Qserv
    • Story Points:
      158
    • WBS:
      02C.06.02.03
    • Team:
      Data Access and Database

      Description

      Need to think through issues related to supporting Level 3 databases

        Attachments

          Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DM-2081 FY19 Implement Missing Features in Qserv for L3

          • Invalid
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-2020 Research how to support L3

          • Done
          mentioned in

          Page Loading...

          Stories in Epic (Custom Issue Matrix)

          Key Summary Story Points Assignee Status
          DM-3505

          Modify czar to use per query CSS metadata

          		 6 Unassigned To Do

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            jbecla Jacek Becla added a comment -

            Briefly discussed L3 loading at 02/06/2015 DM AHM. Concluded: it is ok to lock entire database when locking. In initial implementation. If that proves to be too limiting, will switch to more complicated model and will do per-table locking

            Show
            jbecla Jacek Becla added a comment - Briefly discussed L3 loading at 02/06/2015 DM AHM. Concluded: it is ok to lock entire database when locking. In initial implementation. If that proves to be too limiting, will switch to more complicated model and will do per-table locking
            Hide
            Permalink
            fritzm Fritz Mueller added a comment -

            Malformed issue with not enough information (what does it mean to "revisit", and when is that claimed done?)  We have a plan in place for "formerly-referred-to-as-L3" data – to be ingested with new ingest system, which is an online operation.

            Show
            fritzm Fritz Mueller added a comment - Malformed issue with not enough information (what does it mean to "revisit", and when is that claimed done?)  We have a plan in place for "formerly-referred-to-as-L3" data – to be ingested with new ingest system, which is an online operation.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              fritzm Fritz Mueller
              Watchers:
              Fritz Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.