[
https://issues.apache.org/jira/browse/KYLIN-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhao jintao updated KYLIN-3975:
-------------------------------
Description:
Hi team:
In bigdata analytics platform, we often query data of the nature week or nature
month.
For example, in Bank or Accounting reports, the query periods are often a
natural week or natural month report.
In kylin system, we can build cube to increase query speed. However, it will
query slowly if the amount of data is large and the query cycle is long
especlially using count distinct measure.
For example, We can add month dimension to the cube, then merge cube in normal
month peroid; but if the query sql has date partition, it will also match the
cube has both week dimension and date dimension, kylin need search data from
HBase and aggregate data in memory. It also slowly if the amountof data is
large.
Does anyone face the same problem? Who has a better way to solve the problems
of nature week or nature month query?
Best regards
Thank you.
was:
Hi team:
In bigdata analytics platform, we often query data of the nature week or nature
month.
For example, in Bank or Accounting reports, the query periods are often a
natural week or natural month report.
In kylin system, we can build cube to increase query speed. However, it will
query slowly if the amount of data is large and the query cycle is long
especlially using count distinct measure.
For example, We can add month dimension to the cube, then merge cube in normal
month peroid; but if the query sql has date partition, it will also match the
cube has both week dimension and date dimension, kylin need search data from
HBase and aggregate data in memory. It also slowly if the amountof data is
large.
Does anyone face the same problem? Who has a better way to solve the problems
of nature week or nature month query?
> Can kylin accelerate query speed for natural week or natural month report?
> ---------------------------------------------------------------------------
>
> Key: KYLIN-3975
> URL: https://issues.apache.org/jira/browse/KYLIN-3975
> Project: Kylin
> Issue Type: New Feature
> Components: Job Engine, Query Engine
> Reporter: zhao jintao
> Priority: Major
>
> Hi team:
> In bigdata analytics platform, we often query data of the nature week or
> nature month.
> For example, in Bank or Accounting reports, the query periods are often a
> natural week or natural month report.
> In kylin system, we can build cube to increase query speed. However, it will
> query slowly if the amount of data is large and the query cycle is long
> especlially using count distinct measure.
> For example, We can add month dimension to the cube, then merge cube in
> normal month peroid; but if the query sql has date partition, it will also
> match the cube has both week dimension and date dimension, kylin need search
> data from HBase and aggregate data in memory. It also slowly if the amountof
> data is large.
> Does anyone face the same problem? Who has a better way to solve the problems
> of nature week or nature month query?
>
> Best regards
> Thank you.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
