d statistics information for each hbase RPC, please check
>>> which request take a lot of time or scan too much row. You may check the
>>> following aspects:
>>>
>>> 1. Did your sql query hit the right/best match cuboid?
>>>
>>> 2. Could you try to change the order of R
ay try to cut some segment into
>> more small ones(improve the degree of parallelism)?
>>
>>
>>
>> *Step 3. Do query server side aggregation and decode.*
>>
>>
>>
>> From the last rpc statistics log to final query statistics info .
>>
> From the last rpc statistics log to final query statistics info .
>
>2019-11-28 20:02:10,966 INFO [Query
> 77b0da35-a6e8-d6f9-cd50-152b4d7b0c5a-62] service.QueryService:491 : Stats
> of SQL response: isException: false, duration: 21170, total scan count
> 156
.org"
主题: Need advice and best practices for Kylin query tuning (not cube tuning)
Dear All,
We are troubleshooting slow queries in our Kylin deployment, and we suspect
that the issue is not with the cube definitions, but with our queries. At least
we have some quite complex queries with a
Hi Andras,
Is this specific to real-time streaming, or it is also related to the
normal batch cube? I want to narrow down the scope. Besides, how complex
the queries are? I think that may need more inputs. If you can bring some
sample queries that would help to some extend.
Best regards,
