[jira] [Created] (KYLIN-2456) select * query with join returning 0 rows
liyang created KYLIN-2456: - Summary: select * query with join returning 0 rows Key: KYLIN-2456 URL: https://issues.apache.org/jira/browse/KYLIN-2456 Project: Kylin Issue Type: Bug Reporter: liyang Assignee: liyang The root cause is similar to KYLIN-2367. The query: select * from test_kylin_fact inner JOIN edw.test_cal_dt as test_cal_dt ON test_kylin_fact.cal_dt = test_cal_dt.cal_dt inner JOIN test_category_groupings ON test_kylin_fact.leaf_categ_id = test_category_groupings.leaf_categ_id AND test_kylin_fact.lstg_site_id = test_category_groupings.site_id inner JOIN edw.test_sites as test_sites ON test_kylin_fact.lstg_site_id = test_sites.site_id The plan: OLAPToEnumerableConverter OLAPJoinRel(condition=[=($4, $30)], joinType=[left]) OLAPJoinRel(condition=[AND(=($3, $21), =($4, $22))], joinType=[left]) OLAPJoinRel(condition=[=($1, $19)], joinType=[left]) OLAPTableScan(table=[[DEFAULT, TEST_KYLIN_FACT]], fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18]]) OLAPTableScan(table=[[EDW, TEST_CAL_DT]], fields=[[0, 1]]) OLAPTableScan(table=[[DEFAULT, TEST_CATEGORY_GROUPINGS]], fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8]]) OLAPTableScan(table=[[EDW, TEST_SITES]], fields=[[0, 1, 2]]) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2452) Throw NoSuchElementException when AggregationGroup size is 0
[ https://issues.apache.org/jira/browse/KYLIN-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875202#comment-15875202 ] Wang Cheng commented on KYLIN-2452: --- Thanks! > Throw NoSuchElementException when AggregationGroup size is 0 > > > Key: KYLIN-2452 > URL: https://issues.apache.org/jira/browse/KYLIN-2452 > Project: Kylin > Issue Type: Bug >Reporter: Wang Cheng >Assignee: Wang Cheng >Priority: Trivial > Fix For: v2.0.0 > > Attachments: > 0001-KYLIN-2452-validate-there-is-at-least-one-Aggregatio.patch > > > If there is no AggregationGroup in CubeDesc, it can be saved but throwing > NoSuchElementException in build. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (KYLIN-2452) Throw NoSuchElementException when AggregationGroup size is 0
[ https://issues.apache.org/jira/browse/KYLIN-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang Cheng closed KYLIN-2452. - Resolution: Fixed > Throw NoSuchElementException when AggregationGroup size is 0 > > > Key: KYLIN-2452 > URL: https://issues.apache.org/jira/browse/KYLIN-2452 > Project: Kylin > Issue Type: Bug >Reporter: Wang Cheng >Assignee: Wang Cheng >Priority: Trivial > Fix For: v2.0.0 > > Attachments: > 0001-KYLIN-2452-validate-there-is-at-least-one-Aggregatio.patch > > > If there is no AggregationGroup in CubeDesc, it can be saved but throwing > NoSuchElementException in build. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2451) Set HBASE_RPC_TIMEOUT according to kylin.storage.hbase.coprocessor-timeout-seconds
[ https://issues.apache.org/jira/browse/KYLIN-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15874279#comment-15874279 ] Dayue Gao commented on KYLIN-2451: -- LGTM > Set HBASE_RPC_TIMEOUT according to > kylin.storage.hbase.coprocessor-timeout-seconds > -- > > Key: KYLIN-2451 > URL: https://issues.apache.org/jira/browse/KYLIN-2451 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.0.0 > > > Currently if HBASE_RPC_TIMEOUT is shorter than > "kylin.storage.hbase.coprocessor-timeout-seconds", the HBase RPC call will > timeout before coprocessor gives up. Shall let RPC wait longer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-2451) Set HBASE_RPC_TIMEOUT according to kylin.storage.hbase.coprocessor-timeout-seconds
[ https://issues.apache.org/jira/browse/KYLIN-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-2451. --- Resolution: Fixed > Set HBASE_RPC_TIMEOUT according to > kylin.storage.hbase.coprocessor-timeout-seconds > -- > > Key: KYLIN-2451 > URL: https://issues.apache.org/jira/browse/KYLIN-2451 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.0.0 > > > Currently if HBASE_RPC_TIMEOUT is shorter than > "kylin.storage.hbase.coprocessor-timeout-seconds", the HBase RPC call will > timeout before coprocessor gives up. Shall let RPC wait longer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2451) Set HBASE_RPC_TIMEOUT according to kylin.storage.hbase.coprocessor-timeout-seconds
[ https://issues.apache.org/jira/browse/KYLIN-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15874247#comment-15874247 ] liyang commented on KYLIN-2451: --- Please review: https://github.com/apache/kylin/commit/d7ecd6e2f1a87bf82d3cf6645eab013b873dde8d > Set HBASE_RPC_TIMEOUT according to > kylin.storage.hbase.coprocessor-timeout-seconds > -- > > Key: KYLIN-2451 > URL: https://issues.apache.org/jira/browse/KYLIN-2451 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.0.0 > > > Currently if HBASE_RPC_TIMEOUT is shorter than > "kylin.storage.hbase.coprocessor-timeout-seconds", the HBase RPC call will > timeout before coprocessor gives up. Shall let RPC wait longer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2451) Set HBASE_RPC_TIMEOUT according to kylin.storage.hbase.coprocessor-timeout-seconds
[ https://issues.apache.org/jira/browse/KYLIN-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15874231#comment-15874231 ] liyang commented on KYLIN-2451: --- I see. The cube-level coprocessor-timeout-seconds shall take effect. I'll adjust the change. > Set HBASE_RPC_TIMEOUT according to > kylin.storage.hbase.coprocessor-timeout-seconds > -- > > Key: KYLIN-2451 > URL: https://issues.apache.org/jira/browse/KYLIN-2451 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.0.0 > > > Currently if HBASE_RPC_TIMEOUT is shorter than > "kylin.storage.hbase.coprocessor-timeout-seconds", the HBase RPC call will > timeout before coprocessor gives up. Shall let RPC wait longer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2455) Unsupported columntypes in model
Berry Österlund created KYLIN-2455: -- Summary: Unsupported columntypes in model Key: KYLIN-2455 URL: https://issues.apache.org/jira/browse/KYLIN-2455 Project: Kylin Issue Type: Bug Reporter: Berry Österlund Priority: Trivial It's possible to create a model and build a cube on it with unsupported column types. The error will be shown first when you try to access that table. During my tests, I added a BINARY column to one of the lookup tables. I got an error when accessing the lookup table, not before. It should be impossible to add unsupporter column types during model creation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2451) Set HBASE_RPC_TIMEOUT according to kylin.storage.hbase.coprocessor-timeout-seconds
[ https://issues.apache.org/jira/browse/KYLIN-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15874211#comment-15874211 ] Dayue Gao commented on KYLIN-2451: -- Hi [~liyang.g...@gmail.com], I see what's the difference. Our goal is the same, make rpc timeout longer than coprocessor-timeout-seconds. The differences are that previously we override coprocessor-timeout-seconds according to HBASE_RPC_TIMEOUT (please see comment about coprocessor-timeout-seconds in kylin.properties), and now you want to do it oppositely, set HBASE_RPC_TIMEOUT according to coprocessor-timeout-seconds, right? But I would prefer the previously approach because coprocessor-timeout-seconds is a cube level configs but HBASE_RPC_TIMEOUT is a global one. With your approach, use can't choose a larger value at cube level. > Set HBASE_RPC_TIMEOUT according to > kylin.storage.hbase.coprocessor-timeout-seconds > -- > > Key: KYLIN-2451 > URL: https://issues.apache.org/jira/browse/KYLIN-2451 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.0.0 > > > Currently if HBASE_RPC_TIMEOUT is shorter than > "kylin.storage.hbase.coprocessor-timeout-seconds", the HBase RPC call will > timeout before coprocessor gives up. Shall let RPC wait longer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)