Re: Re: Re: Slow Query Performance With 'WHERE' Clause

Thank you Ma, for response and making me correct about query filters( WHERE clause) in Kylin. I got a an idea that Kylin is using HBase FuzzyFilters while

Re:Re: Re: Slow Query Performance With 'WHERE' Clause

Hi Shrikant, Which Kylin version you used? By default, most of the filters will be pushed down to coprocessor, you may grep "Total filtered row:" in your log to see how many rows are filtered from coprocessor side. If you want to change code to add some log there, you can add log at method:

Re: Re: Slow Query Performance With 'WHERE' Clause

Hi Team, I tried debugging code to understand query execution (on Kylin v2.5 hbase 1.x) . As I understood query is formed and executed using Calcite APIs. Could you please help me to get answer of below? 1. With my understanding default implementation of filter operation (WHERE clause)

Re: Re: Slow Query Performance With 'WHERE' Clause

Thank you Ma for response. I didn't find any logs about applying filters in co-processors. Also I don't see logs for logical/physical query plans in kylin.log. Am I missing anything? I would like to put logger statements in code and build specific module(s) as required for tracing latencies --

Re: Slow Query Performance With 'WHERE' Clause

Hi Team, Could you please confirm if filtering of rows (WHERE clause) is done in CoProcessor side? Is there any APIs/logging to get physical plan of query? It will help us in optimising the cube. On Mon, Oct 22, 2018 at 8:58 PM Shrikant Bang wrote: > Thanks ShaoFeng for response.

Re: Slow Query Performance With 'WHERE' Clause

Thanks ShaoFeng for response. I will try this and will update the results of my queries. I would like to learn, how to identify the bottleneck in query executions. Can we trace the query execution in each stage with timestamp? Also is there way we can get physical plan of query? This could help

Re: Slow Query Performance With 'WHERE' Clause

Hi Shrikant, What's the order of the dimensions in the rowkey? In this case, you need to put "d3" at the heading position of the rowkey. Here is a good reference on how to design a cube, maybe we need add that into the FAQ or as a part of document: