You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2017/08/09 03:42:00 UTC

[jira] [Closed] (KYLIN-1617) No table available for query after cube build is successful

     [ https://issues.apache.org/jira/browse/KYLIN-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaofeng SHI closed KYLIN-1617.
-------------------------------

> No table available for query after cube build is successful
> -----------------------------------------------------------
>
>                 Key: KYLIN-1617
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1617
>             Project: Kylin
>          Issue Type: Bug
>            Reporter: liyang
>
> Report by Jason Wang:
> I just finished building a cube in Kylin, and it was successful, but in the Insight page, there is no tables, and if I submit a query, it fails with a table not found error. Notice there are no tables in the left side of the page. I noticed that, when I select the project in the page header, there was a request made to path “/kylin/api/tables_and_columns?project=DeviceMetrics_Prototype”, and the response was an empty JSON array “[]”.
> The problem seems to be caused by stale L2 cache. ProjectManager.isExposedTable() return false for the table.
> Realizing that, I restarted Kylin server, and the tables came up, and I can query them without any problem. Please look into your cache update logic, especially in the case where the cube building is taking extra-long time. In this particular case, the cube build took 12 hours. When I experimented with a smaller cube (40 minutes), I didn’t encounter this issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)