Do you mean extract data from the fact table? Define a model based on this table, and dimensions & this measure, then create an aggregation group with these dimensions and measure, build to get the data you preferred. Or do you mean the metadata file? Just query the database or dump metadata to check what you need.
On Wed, Aug 2, 2023 at 20:22 marc nicole <[email protected]> wrote: > the dataset (csv) is in this form > > att1 > > att2 > > count_measure > str1 > str2 > int1 > ........... > How to extract from it fact table (the count_measure column) and the > dimensions ? in the datasource / model definition in Kylin? > > Le mer. 2 août 2023 à 13:32, marc nicole <[email protected]> a écrit : > >> in the model the measure definition is as follows (I don't understand >> chinese) >> >> { >> "name": "COUNT1", >> "function": { >> "expression": "COUNT", >> "parameter": { >> "type": "column", >> "value": "attributeName.COUNT1" >> }, >> "returntype": "bigint" >> } >> }, >> >> >> Le mer. 2 août 2023 à 05:31, Xiaoxiang Yu <[email protected]> a écrit : >> >>> 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 ?? >>> >>> >>> >>>
