[jira] [Updated] (KYLIN-4137) Accelerate metadata reloading

2019-09-17 Thread nichunen (Jira)


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

nichunen updated KYLIN-4137:

Fix Version/s: (was: v2.6.4)

> Accelerate metadata reloading
> -
>
> Key: KYLIN-4137
> URL: https://issues.apache.org/jira/browse/KYLIN-4137
> Project: Kylin
>  Issue Type: Improvement
>  Components: Metadata
>Affects Versions: v2.6.2
>Reporter: Temple Zhou
>Assignee: Temple Zhou
>Priority: Minor
> Fix For: v3.0.0-beta
>
>
> Now, org.apache.kylin.metadata.cachesync.CachedCrudAssist#reloadAll is using 
> an inappropriate method to deal with MySQLJdbcMetadata.
> As the every call of reloadAt(path) will access the database, which is almost 
> fine to HBase but really unfriendly to the MySQL(RDBMS).
> I think we should get all of the resource with single request instead of the 
> separate request to get every resource.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (KYLIN-4137) Accelerate metadata reloading

2019-08-15 Thread nichunen (JIRA)


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

nichunen updated KYLIN-4137:

Fix Version/s: (was: v2.6.4)
   v3.0.0-beta

> Accelerate metadata reloading
> -
>
> Key: KYLIN-4137
> URL: https://issues.apache.org/jira/browse/KYLIN-4137
> Project: Kylin
>  Issue Type: Improvement
>  Components: Metadata
>Affects Versions: v2.6.2
>Reporter: Temple Zhou
>Assignee: Temple Zhou
>Priority: Minor
> Fix For: v3.0.0-beta
>
>
> Now, org.apache.kylin.metadata.cachesync.CachedCrudAssist#reloadAll is using 
> an inappropriate method to deal with MySQLJdbcMetadata.
> As the every call of reloadAt(path) will access the database, which is almost 
> fine to HBase but really unfriendly to the MySQL(RDBMS).
> I think we should get all of the resource with single request instead of the 
> separate request to get every resource.



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


[jira] [Updated] (KYLIN-4137) Accelerate metadata reloading

2019-08-13 Thread Temple Zhou (JIRA)


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

Temple Zhou updated KYLIN-4137:
---
Affects Version/s: (was: v2.6.0)
   (was: v2.5.0)
   (was: v2.4.0)
   (was: v2.3.0)
   (was: v2.2.0)
  Description: 
Now, org.apache.kylin.metadata.cachesync.CachedCrudAssist#reloadAll is using an 
inappropriate method to deal with MySQLJdbcMetadata.

As the every call of reloadAt(path) will access the database, which is almost 
fine to HBase but really unfriendly to the MySQL(RDBMS).

I think we should get all of the resource with single request instead of the 
separate request to get every resource.

  was:
The logic to generate the table resource path had changed since Kylin 2.2.0, so 
the table loaded(or reload) after Kylin 2.2.0 will use this format – 
/table/table_name–project_name.json.

However, the resource path with former format( /table/table_name.json) will 
still exists, which can lead to failed loading during startup progress probably.

So, we should cleanup the expired and redundant table resource path.

   Issue Type: Improvement  (was: Bug)
  Summary: Accelerate metadata reloading  (was: Delete expired 
table resource path in metastore)

> Accelerate metadata reloading
> -
>
> Key: KYLIN-4137
> URL: https://issues.apache.org/jira/browse/KYLIN-4137
> Project: Kylin
>  Issue Type: Improvement
>  Components: Metadata
>Affects Versions: Future
>Reporter: Temple Zhou
>Assignee: Temple Zhou
>Priority: Minor
>
> Now, org.apache.kylin.metadata.cachesync.CachedCrudAssist#reloadAll is using 
> an inappropriate method to deal with MySQLJdbcMetadata.
> As the every call of reloadAt(path) will access the database, which is almost 
> fine to HBase but really unfriendly to the MySQL(RDBMS).
> I think we should get all of the resource with single request instead of the 
> separate request to get every resource.



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