Hi Dong, Well I have dropped all the existing cubes so I am just left with the single cube for the reference table which I have build just now. Project Name is Testing and cube name is sc_sd_esd_diff_3, specific Details for the cube is mentioned below,
Fact Table : fct Dimensions: (Type is normal for all) ft.cc ft.sm ft.fcc ft.fm ft.st ft.sodp Measures: (Expression is Sum and Return Type is bigint) _count_ (Expression is count AND param type is constant param value is 1) ft.lmtdf ft.mtdf ft.modf ft.zdf ft.odf ft.tdf ft.gtdf Refresh Setting: ft.fsc.vdp Agg. Group : ft.cc ft.sm ft.fcc ft.fm ft.st ft.sodp Rowkeys : (Same as Agg Group with Mandatory:N AND Dictionary:true AND length:0) Kindly let me know if you require some other information as well. Thanks, On Tue, Jun 16, 2015 at 5:58 PM, dong wang <[email protected]> wrote: > "Can't find any realization" means that none of the existing cubes match > the levels in both "select" and "group by" parts. What's your project's > name and cube's name? and is there more info about your cube's definition? > note that you can only select a subset columns of the cube~ > > 2015-06-16 20:19 GMT+08:00 Vineet Mishra <[email protected]>: > > > Moreover would like to add that sometimes I am getting this error in > > kylin.log, > > > > [http-bio-7070-exec-29]:[2015-06-16 > > > > > 17:46:38,317][ERROR][org.apache.kylin.rest.controller.TableController.cloneTableDesc(TableController.java:172)] > > - The result cardinality is not identical with hive table metadata, > > cardinaly : > > > > > 11050893,3828574,16019,42748,973708,620,281095,1392176,54,31888,2115197,1575939,1422740,2195,7,76,3,35731,5,270 > > column array length: 54 > > [http-bio-7070-exec-29]:[2015-06-16 > > > > > 17:46:38,318][INFO][org.apache.kylin.rest.controller.TableController.getHiveTables(TableController.java:74)] > > - Return all table metadata in 1 seconds > > [http-bio-7070-exec-29]:[2015-06-16 > > > > > 17:46:39,494][ERROR][org.apache.kylin.rest.controller.TableController.cloneTableDesc(TableController.java:172)] > > - The result cardinality is not identical with hive table metadata, > > cardinaly : > > > > > 11050893,3828574,16019,42748,973708,620,281095,1392176,54,31888,2115197,1575939,1422740,2195,7,76,3,35731,5,270 > > column array length: 54 > > > > Thanks, > > > > On Tue, Jun 16, 2015 at 5:45 PM, Vineet Mishra <[email protected]> > > wrote: > > > > > Any update on this? > > > > > > URGENT! > > > > > > On Tue, Jun 16, 2015 at 4:05 PM, Vineet Mishra <[email protected] > > > > > wrote: > > > > > >> Hi All, > > >> > > >> While I have build the cube, I am trying to query through the kylin > > query > > >> interface but landing up in some error. Stack trace mentioned below, > > >> > > >> Query: > > >> SELECT ft.cc ,ft.sm ,ft.fcc ,ft.fm ,ft.st ,ft.sodp ,ft.lmtdf ,ft.mtdf > > >> ,ft.modf ,ft.zdf ,ft.odf ,ft.tdf ,ft.gtdf, count(1) as counts FROM > > >> STAGE.fsc as ft group by ft.cc ,ft.sm ,ft.fcc ,ft.fm ,ft.st ,ft.sodp > > >> ,ft.lmtdf ,ft.mtdf ,ft.modf ,ft.zdf ,ft.odf ,ft.tdf ,ft.gtdf > > >> > > >> Exception: > > >> org.apache.kylin.query.routing.NoRealizationFoundException: Can't find > > >> any realization. Please confirm with providers. SQL digest: fact table > > >> STAGE.fsc,group by [STAGE.fsc.cc, STAGE.fsc.sm, STAGE.fsc.fcc, > > >> STAGE.fsc.fm, STAGE.fsc.st, STAGE.fsc.sodp, STAGE.fsc.lmtdf, > > >> STAGE.fsc.mtdf, STAGE.fsc.modf, STAGE.fsc.zdf, STAGE.fsc.odf, > > >> STAGE.fsc.tdf, STAGE.fsc.gtdf],filter on [],with > aggregates[FunctionDesc > > >> [expression=COUNT, parameter=null, returnType=null]] > > >> > > >> Moreover I am referring the code where this error is getting thrown > link > > >> mentioned below, > > >> > > >> > > >> > > > https://github.com/KylinOLAP/Kylin/blob/master/query/src/main/java/org/apache/kylin/query/routing/QueryRouter.java > > >> > > >> in the code there's a reference to Project Manager class(as > highlighted > > >> above), I can see the class being instantiated within this class but > > >> nowhere I can find the definition of Project Manager Class. Is this > > class > > >> kept unrevealed in the project. > > >> > > >> Awaiting response on priority. > > >> > > >> Thanks! > > >> > > > > > > > > >
