[
https://issues.apache.org/jira/browse/KYLIN-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiting Guo updated KYLIN-5945:
-------------------------------
Description:
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.
was:
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.
> 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
>
>
> 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)
