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

"SELECT DISTINCT foo FROM LSST.Filter AS f" shouldn't require a merge step

    XMLWordPrintable

Details

    • Bug
    • Status: Invalid
    • Resolution: Done
    • None
    • Qserv
    • None

    Description

      This query is non-chunked so the QuerySession.needMerge flag should be set to false

      (grep ticket number in core/ to get the unit test where this issue appear)

      Attachments

        Issue Links

          Activity

            According to npease, in the current design, all queries have a merge step (e.g. to accommodate column renaming). This suggested optimization is no longer relevant.

            fritzm Fritz Mueller added a comment - According to npease , in the current design, all queries have a merge step (e.g. to accommodate column renaming). This suggested optimization is no longer relevant.

            People

              Unassigned Unassigned
              jammes Fabrice Jammes
              Fritz Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.