[jira] [Updated] (KYLIN-4085) Segment parallel building may cause segment not found

2019-07-17 Thread Chao Long (JIRA)


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

Chao Long updated KYLIN-4085:
-
Fix Version/s: (was: v3.0.0)
   v3.0.0-beta

> Segment parallel building may cause segment not found
> -
>
> Key: KYLIN-4085
> URL: https://issues.apache.org/jira/browse/KYLIN-4085
> Project: Kylin
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Chao Long
>Assignee: Chao Long
>Priority: Major
> Fix For: v3.0.0-beta
>
>
> In the case of multi-node and parallel building one same cube, the 
> JDBCResourceStore split the update metadata step in two sql, which can't 
> guarantee the atomicity.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (KYLIN-4085) Segment parallel building may cause segment not found

2019-07-17 Thread Chao Long (JIRA)


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

Chao Long updated KYLIN-4085:
-
Fix Version/s: (was: v3.0.0-alpha2)
   v3.0.0

> Segment parallel building may cause segment not found
> -
>
> Key: KYLIN-4085
> URL: https://issues.apache.org/jira/browse/KYLIN-4085
> Project: Kylin
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Chao Long
>Assignee: Chao Long
>Priority: Major
> Fix For: v3.0.0
>
>
> In the case of multi-node and parallel building one same cube, the 
> JDBCResourceStore split the update metadata step in two sql, which can't 
> guarantee the atomicity.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (KYLIN-4085) Segment parallel building may cause segment not found

2019-07-17 Thread Chao Long (JIRA)


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

Chao Long updated KYLIN-4085:
-
Fix Version/s: v3.0.0-alpha2

> Segment parallel building may cause segment not found
> -
>
> Key: KYLIN-4085
> URL: https://issues.apache.org/jira/browse/KYLIN-4085
> Project: Kylin
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Chao Long
>Assignee: Chao Long
>Priority: Major
> Fix For: v3.0.0-alpha2
>
>
> In the case of multi-node and parallel building one same cube, the 
> JDBCResourceStore split the update metadata step in two sql, which can't 
> guarantee the atomicity.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (KYLIN-4085) Segment parallel building may cause segment not found

2019-07-15 Thread Chao Long (JIRA)


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

Chao Long updated KYLIN-4085:
-
Description: In the case of multi-node and parallel building one same cube, 
the JDBCResourceStore split the update metadata step in two sql, which can't 
guarantee the atomicity.

> Segment parallel building may cause segment not found
> -
>
> Key: KYLIN-4085
> URL: https://issues.apache.org/jira/browse/KYLIN-4085
> Project: Kylin
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Chao Long
>Assignee: Chao Long
>Priority: Major
>
> In the case of multi-node and parallel building one same cube, the 
> JDBCResourceStore split the update metadata step in two sql, which can't 
> guarantee the atomicity.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)