hello See this Video: <https://youtu.be/v9of5N3TcTw>
Query with *limit 5*, the preview data run OK, but load data ... never finished Somebody has tested Kylin with New Microsoft Power Bi Desktop ? 2016-09-14 11:54 GMT+02:00 Alberto Ramón <[email protected]>: > The cube is the Kylin Example, the fact table have 9.800 Row, and return > time to Kylin UI are 0.3 Seconds > and CATEGORY_GROUPINGS has 144 rows > > ==> I think isnt't a performance problem > > *sound like , cast problem, overflow of int, or Nulls* > But I don't Know the which Row / Column have a problematic Value in any > log :( > > 2016-09-14 8:08 GMT+02:00 Abhilash L L <[email protected]>: > >> Hello Alberto, >> >> When the request is made via the Kylin UI, it adds an 'accept >> partial' flag, which is similar to a 'limit' in sql world. >> >> When the query is being sent over odbc, kylin server is expected to >> send all the records as the output >> >> Please check the thread titled 'kylin cube performance' for more >> information. >> >> Regards, >> Abhilash >> >> On Wed, Sep 14, 2016 at 10:48 AM, Alberto Ramón < >> [email protected]> wrote: >> >>> I found this >>> From Kylin ODBC LOG: >>> >>> *[INFO ][2016-09-14.06:48:47]select "PART_DT", * >>> * "LEAF_CATEG_ID", * >>> * "LSTG_SITE_ID", * >>> * "LSTG_FORMAT_NAME", * >>> * "PRICE", * >>> * "SELLER_ID" * >>> *from "DEFAULT"."KYLIN_SALES"* >>> *[ERROR][2016-09-14.06:49:53]The REST query request failed, the error >>> message is: Error while executing SQL "select "PART_DT", >>> "LEAF_CATEG_ID", "LSTG_SITE_ID", "LSTG_FORMAT_NAME", >>> "PRICE", "SELLER_ID" from "DEFAULT"."KYLIN_SALES"": Timeout visiting >>> cube!* >>> >>> This querie *from Microsoft, never finish* or kill my HBase, but from >>> Kylin UI works fine < 0.5 sec >>> >>> 2016-09-14 6:49 GMT+02:00 Alberto Ramón <[email protected]>: >>> >>>> Hello >>>> I tested New Microsoft Power BI with Kylin >>>> [image: Imágenes integradas 1] >>>> With KYLIN_CAL_DT connector can read data: >>>> [image: Imágenes integradas 2] >>>> >>>> >>>> But with KYLIN GROUPING AND SALES: >>>> And I have this error >>>> >>>> Unexpected error: *Value was either too large or too small for an >>>> Int32.* >>>> Details: >>>> Microsoft.Mashup.Evaluator.Interface.ErrorException: Value was >>>> either too large or too small for an Int32. ---> >>>> Microsoft.Mashup.Evaluator.Interface.ErrorException: Value was either >>>> too large or too small for an Int32. ---> >>>> Microsoft.Mashup.Evaluator.Interface.ErrorException: Value was either >>>> too large or too small for an Int32. ---> >>>> Microsoft.Mashup.Evaluator.Interface.ErrorException: Value was either >>>> too large or too small for an Int32. ---> >>>> Microsoft.Mashup.Evaluator.Interface.ErrorException: Value was either >>>> too large or too small for an Int32. ---> System.OverflowException: Value >>>> was either too large or too small for an Int32. ---> >>>> System.OverflowException: Value was either too large or too small for an >>>> Int32. >>>> at System.Convert.ToInt32(Int64 value) >>>> at Microsoft.Mashup.Engine1.Library.Odbc.OdbcDataReaderExtensio >>>> ns.GetNullableInt32(IDataReader reader, Int32 ordinal) >>>> >>>> >>>> Some idea? >>>> In true, I have also problems of connectivity using:Qlik and Sisense >>>> Software >>>> >>> >>> >> >
