Uploaded image for project: 'Kylin'
  1. Kylin
  2. KYLIN-1622

sql not executed and report topN error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • v1.5.2
    • Query Engine
    • None

    Description

      pull the latest code from master branch, commit id is d899a67963af14f80fc047a9253ac7736c1983f3,
      package and deploy in sandbox, and run bin/sample.sh to get sample cube "kylin_sales_cube", and created a cube called "kylin_sales_cube_desc_TOPN". I build "kylin_sales_cube_desc_TOPN" first and then build "kylin_sales_cube".

      topN sql is
      "
      SELECT
      SUM (t0.PRICE), t1.WEEK_BEG_DT
      FROM "DEFAULT".KYLIN_SALES AS t0
      INNER JOIN "DEFAULT".KYLIN_CAL_DT AS t1
      ON t0.PART_DT = t1.CAL_DT
      GROUP BY
      t1.WEEK_BEG_DT
      ORDER BY SUM (t0.PRICE)
      "
      but !!!
      when run sql
      "
      SELECT
      t1.WEEK_BEG_DT
      FROM "DEFAULT".KYLIN_SALES AS t0
      INNER JOIN "DEFAULT".KYLIN_CAL_DT AS t1
      ON t0.PART_DT = t1.CAL_DT
      GROUP BY
      t1.WEEK_BEG_DT
      "
      it reports
      Error while executing SQL "SELECT t1.WEEK_BEG_DT FROM "DEFAULT".KYLIN_SALES AS t0 INNER JOIN "DEFAULT".KYLIN_CAL_DT AS t1 ON t0.PART_DT = t1.CAL_DT GROUP BY t1.WEEK_BEG_DT LIMIT 50000": When query with topN, only one metrics is allowed.

      I'll attach kylin_sales_cube_desc_TOPN.json
      for "kylin_sales_cube" you can run bin/sample.sh

      Attachments

        Activity

          People

            shaofengshi Shao Feng Shi
            zhongjian Jason Zhong
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: