<node id="631822">
  <nid>631822</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1580309603</created>
  <changed>1580912322</changed>
  <title><![CDATA[Phd Proposal by Qi Zhou]]></title>
  <body><![CDATA[<p><strong>Title:&nbsp;</strong>Automated Reasoning for Multi-Query Optimization</p>

<p>&nbsp;</p>

<p><strong>Date:</strong>&nbsp;Tuesday, February 4, 2020</p>

<p><strong>Time:&nbsp;</strong>01:00 PM - 02:30 PM (EST)</p>

<p><strong>Location:&nbsp;</strong>Klaus <strong>1212</strong></p>

<p>&nbsp;</p>

<p><strong>Qi Zhou</strong></p>

<p>Ph.D. Student</p>

<p>School of Computer Science</p>

<p>Georgia Institute of Technology</p>

<p>&nbsp;</p>

<p><strong>Committee:</strong></p>

<p>Dr. William Harris (advisor) -&nbsp;Galois Inc.</p>

<p>Dr. Joy Arulraj (co-advisor) - School of Computer Science, Georgia Institute of Technology</p>

<p>Dr. Shamkant B.Navathe - School of Computer Science, Georgia Institute of Technology</p>

<p>Dr. Alex Orso - School of Computer Science, Georgia Institute of Technology</p>

<p>Dr. John Regehr - School of Computing, University of Utah</p>

<p>&nbsp;</p>

<p><strong>Abstract:</strong></p>

<p>The advent of DataBase-as-a-Service (DBaaS) platforms has increased the importance of multi-query optimization.&nbsp;</p>

<p>These services enable users to quickly create and deploy complex data processing pipelines. However, in practice, these pipelines often exhibit a significant overlap of computation due to the redundant execution of certain SQL queries. We seek to optimize the execution of a collection of queries by identifying and eliminating overlapping computations.</p>

<p>&nbsp;</p>

<p>In this proposal, I will present two techniques for efficiently and effectively proving the equivalence of queries. I will first present a symbolic approach to tackle this problem that relies on SMT solver. While this technique covers a wider array of SQL features compared to prior algebraic approaches, it can neither support structurally-different queries nor prove equivalence under bag semantics,&nbsp;the underlying model of all modern database applications.&nbsp;I will next introduce a two-stage verification algorithm with a novel symbolic representation combined with the algebraic approach to circumvent these limitations.</p>

<p>&nbsp;</p>

<p>In practice, even queries that are not equivalent tend to have overlapping computation. I propose to design a technique for&nbsp;determining containment relationships between non-equivalent queries. Furthermore, I propose to leverage this technique for augmenting a multi-query optimizer by&nbsp;automatically synthesizing queries that can leverage the results of prior queries.&nbsp;&nbsp;</p>

<p>&nbsp;</p>
]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Automated Reasoning for Multi-Query Optimization]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2020-02-04T13:00:00-05:00]]></value>
      <value2><![CDATA[2020-02-04T15:00:00-05:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Faculty/Staff]]></value>
      </item>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
          <item>
        <value><![CDATA[Graduate students]]></value>
      </item>
          <item>
        <value><![CDATA[Undergraduate students]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>221981</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Graduate Studies]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>102851</tid>
        <value><![CDATA[Phd proposal]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
