Could you post more log here? As attachment if you prefer clean email. Want the log from query start to its end, for both success case and failure case. It could be something about fuzzy key optimization or about coprocessor. Need more log to pin it down.
On Thu, Jan 14, 2016 at 12:01 AM, James Jones <[email protected]> wrote: > Kylin versions have been both 1.1.1 and 1.2. > > Just noticed that kylin support explain plan for... Not sure if this helps > but here is the output for on of the queries that times out. > > OLAPToEnumerableConverter > > OLAPAggregateRel(group=[{0, 1}], SPEND=[SUM($2)], TRIPS=[SUM($3)]) > > OLAPProjectRel(EXPR$0=[CAST($0):VARCHAR(6) CHARACTER SET "UTF-16LE" > COLLATE "UTF-16LE$en_US$primary"], ADVERTISERID=[$2], SPEND=[$7], > TRIPS=[$6]) > > OLAPFilterRel(condition=[AND(OR(=($1, '30300'), =($1, '30301'), > =($1, '30302'), =($1, '30303'), =($1, '30304'), =($1, '30305'), =($1, > '30306'), =($1, '30307'), =($1, '30060'), =($1, '30061'), =($1, '30062'), > =($1, '30063'), =($1, '30064'), =($1, '30065'), =($1, '30066'), =($1, > '30067')), OR(=($2, 22150), =($2, 35010)), >=($0, 20150101), <=($0, > 20150827))]) > > OLAPJoinRel(condition=[=($1, $20)], joinType=[inner]) > > OLAPJoinRel(condition=[=($0, $11)], joinType=[inner]) > > OLAPTableScan(table=[[FACT, SPENDTRIPINC]], fields=[[0, 1, 2, > 3, 4, 5, 6, 7, 8]]) > > OLAPTableScan(table=[[FACT, CALENDARDATES]], fields=[[0, 1, > 2]]) > > OLAPTableScan(table=[[FACT, FLATGEO2]], fields=[[0, 1, 2, 3, 4, > 5, 6, 7, 8]]) > > On Tue, Jan 12, 2016 at 4:50 AM, Li Yang <[email protected]> wrote: > >> What's the Kylin version? >> >> The many IN filter has been through a couple of optimizations. Want to >> make sure you are on latest code. >> >> On Fri, Jan 8, 2016 at 4:37 AM, James Jones <[email protected]> wrote: >> >>> The example below works great >>> select column(s) >>> from table >>> where column in (val1,val2,val3,...val50) >>> >>> However when I try to do something like: >>> select column(s) >>> from table >>> where column1 in (val1,val2,val3,...val50) >>> and column2 in (val1,val2) >>> >>> I receive a value timeout exception. >>> *ScannerTimeoutException: 342556ms passed since the last invocation, >>> timeout is currently set to 60000* >>> >>> >>> >>> When watching the kylin_query log I've noticed the query will work when >>> I see something like: >>> >>> Scan hbase cubiod exact match >>> Start: \x00 .... >>> Stop: \x00 .... >>> Fuzzy \x00 ... >>> >>> When the second in operator is in use the Hbase scan doesn't display the >>> Fuzzy data. >>> >>> Scan hbase table KYLIN_O03ZWB4DK9: cuboid exact match, from 57344 to >>> 57344 >>> Start: \x00\x00\x00\x00\x00\x00\xE0\x00\x04\x48\x30\xBB\x00\xB2 - >>> \x00\x00\x00\x00\x00\x00\xE0\x00\x04H0\xBB\x00\xB2 >>> Stop: \x00\x00\x00\x00\x00\x00\xE0\x00\x05\x36\x31\xAB\x03\x8D\x00 - >>> \x00\x00\x00\x00\x00\x00\xE0\x00\x0561\xAB\x03\x8D\x00 >>> >>> Then starts the next scan. >>> >> >> >
