Hello, We plan to upgrade to Kylin 1.5.x series from 1.2 series. We want to ask the team a few questions / clarification before proceeding. Since we are looking at upgrading, please do let us know the behaviour for the latest 1.5.x release.
1) Updating facts Eg: Lets say im building a cube for jira tickets. List of tickets is my fact table. List of ticket status is my dimension table. Now if a ticket is updated from 'open' to 'in progress' how to tell kylin this change ? 2) Multiple dimensions in memory When we were on 1.2 versions, all the dimensions were kept in memory. So memory always keeps increasing. The in memory dimensions were not swapped in / out, causing tomcat OOM issues. Is this still the same in 1.5.x ? 3) Do these dimension snapshots get reloaded on a cube refresh / data appended ? 4) Maximum size for dimension There was an older thread talking about 300mb max snapshot size. Does this limitation still hold? Do very high cardinality dimension still build the trees on one node ? 5) Multiple query servers When there are multiple query servers, will one query server serve only one cube or all servers serve all cubes. If its one cube only in one server, how does kylin handle a server going down. 6) Incremental build Is there a document on how incremental build works ? We want to understand limitations / assumptions for this. Regards, Abhilash
