[ 
https://issues.apache.org/jira/browse/KYLIN-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870061#comment-17870061
 ] 

ASF subversion and git services commented on KYLIN-5945:
--------------------------------------------------------

Commit 03e5a29ee23763446ce4f6310265ac2304c11ed0 in kylin's branch 
refs/heads/kylin5 from Zhiting Guo
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=03e5a29ee2 ]

KYLIN-5945 Metadata refactor

--------------
Co-authored-by: Zhiting Guo <[email protected]>
Co-authored-by: hellozepp <[email protected]>


> metadata refactor
> -----------------
>
>                 Key: KYLIN-5945
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5945
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Metadata
>    Affects Versions: 5.0-alpha
>            Reporter: pengfei.zhan
>            Assignee: pengfei.zhan
>            Priority: Major
>             Fix For: 5.0.0
>
>         Attachments: Metadata deep dive (en).pdf, metadata (3).pdf
>
>
> Kylin's metadata has some architectural issues, such as: 
> 1. The metadata adopts a key-value structure. The JSON block contains a lot 
> of content, which will grow with the growth of customer business, resulting 
> in excessive network IO when updating metadata.
> 2. The design of epoch and project lock ensures that transactions within the 
> project are executed serially, resulting in single-point bottlenecks and 
> concurrency problems.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to