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

Clean up QuerySession-related code in czar



    • Story
    • Status: To Do
    • Resolution: Unresolved
    • None
    • Qserv
    • None


      (created in response to DM-211)
      This ticket should address the following inelegancies in the qserv-czar.

      • QuerySession->QueryPipeline. The "session" abstraction has moved to a better place. The iterator portion should be shifted into its own separate class, though perhaps still associated with QueryPipeline. The iterator portion's new home should be amenable to eventually moving the actual query materialization to the worker, though we shouldn't introduce new abstractions until we are actually ready to move the substitution/materialization to the worker.
      • QueryContext needs to be split into incoming external QueryContext and a sort of QueryClipboard for passing information between analysis/manipulation plugins. Eventually, I imagine a chain/tree of them attached to the select statements themselves in order to represent subquery scope nesting (which is complicated to represent and to reason about--nesting and the resulting namespace resolution is tricky), but I don't think we should try doing the chaining in the first phase. For this ticket, create QueryClipboard to hold the portion for interchange between analysis plugins. Query analysis plugins would then pass this object (which points at an immutable? QueryContext) between themselves. QueryClipboard probably should live in qana, QueryContext in query (unless there is a good reason to move it).


        Issue Links



              Unassigned Unassigned
              fritzm Fritz Mueller
              Fritz Mueller
              0 Vote for this issue
              1 Start watching this issue




                  No builds found.