????
------------------ ???????? ------------------ ??????: "??????"<[email protected]>; ????????: 2023??8??2??(??????) ????3:45 ??????: "user"<[email protected]>; ????: Re: measure column showing 1 as values instead of the actual values in Kylin SQL Query answer table ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?????? [email protected] ---- Replied Message ---- From P.F. ZHAN<[email protected]> Date 8/2/2023 15:34 To <[email protected]> Subject Re: measure column showing 1 as values instead of the actual values in Kylin SQL Query answer table ????????????????????????????????????????????????????????cube????cube?????????????????????????????????????????? On Wed, Aug 2, 2023 at 11:35 ?????? <[email protected]> wrote: ??????????????????????????????????????????????????????????????????????kylin4.0.3?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?????? [email protected] ---- Replied Message ---- From Xiaoxiang Yu<[email protected]> Date 8/2/2023 11:31 To <[email protected]> , <[email protected]> Subject Re:measure column showing 1 as values instead of the actual values in Kylin SQL Query answer table Do you check the answer by Hive/SparkSQL, do Hive/SparkSQL give the expected answer? If you have checked, I think you can give us you cube defination(CubeDesc in Json) and the SQL statement you queried, so we can discuss in detail? -- Best wishes to you ! From ??Xiaoxiang Yu At 2023-08-02 04:35:04, "marc nicole" <[email protected]> wrote: The measure is of type column (not constant) and is bigint. I selected the measure from the dropdown corretly as well. measure column returns 1 for all column values instead of actual values when querying the cube. What could be the underlying problem? cube or model defining? or maybe data source attribute types? Maybe I should create a lookup table with the fact table (which I am not doing so far)? Why the measure column in query answer is showing only 1 as values ??
