[jira] [Commented] (ATLAS-856) Lazy-load type cache provider
[
https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343039#comment-15343039
]
ATLAS QA commented on ATLAS-856:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812243/ATLAS-856.patch
against master revision 7666ae9.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/348//console
This message is automatically generated.
> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
> Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: ATLAS-856.patch, rb48565.patch
>
>
> A modified version of the default local cache provider which will run a
> lookup on the backend storage if a requested type is not found in the cache,
> and load it in the cache and return it if it's found. This lazy-loading cache
> would cover the case where new types are registered, not the case where
> existing types are modified, while avoiding the deployment/maintenance and
> performance impact of a distributed cache in an HA environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-856) Lazy-load type cache provider
[ https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342283#comment-15342283 ] David Kantor commented on ATLAS-856: [~shwethags] Yes your changes make sense, good idea to use Configuration and mutate the property setting needed for the tests. I noticed your patch does a delete and add of classes that I renamed. Rather than lose the history of those renamed modules, I will apply your changes in my source, and upload a new set of changes to review board and attach an updated. That way the renames will be recorded in git correctly. Thanks very much for your help on this. > Lazy-load type cache provider > - > > Key: ATLAS-856 > URL: https://issues.apache.org/jira/browse/ATLAS-856 > Project: Atlas > Issue Type: New Feature >Reporter: David Kantor >Assignee: David Kantor > Attachments: ATLAS-856.patch, rb48565.patch > > > A modified version of the default local cache provider which will run a > lookup on the backend storage if a requested type is not found in the cache, > and load it in the cache and return it if it's found. This lazy-loading cache > would cover the case where new types are registered, not the case where > existing types are modified, while avoiding the deployment/maintenance and > performance impact of a distributed cache in an HA environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-856) Lazy-load type cache provider
[ https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342221#comment-15342221 ] Shwetha G S commented on ATLAS-856: --- [~dkantor], the attached patch has some changes to not create atlas-application.properties in respository/test. See if the changes make sense to you > Lazy-load type cache provider > - > > Key: ATLAS-856 > URL: https://issues.apache.org/jira/browse/ATLAS-856 > Project: Atlas > Issue Type: New Feature >Reporter: David Kantor >Assignee: David Kantor > Attachments: ATLAS-856.patch, rb48565.patch > > > A modified version of the default local cache provider which will run a > lookup on the backend storage if a requested type is not found in the cache, > and load it in the cache and return it if it's found. This lazy-loading cache > would cover the case where new types are registered, not the case where > existing types are modified, while avoiding the deployment/maintenance and > performance impact of a distributed cache in an HA environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-856) Lazy-load type cache provider
[
https://issues.apache.org/jira/browse/ATLAS-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333123#comment-15333123
]
ATLAS QA commented on ATLAS-856:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12810859/rb48565.patch
against master revision 39eb9f1.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
+1 checkstyle. The patch generated 0 code style errors.
{color:red}-1 findbugs{color}. The patch appears to introduce 380 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.atlas.discovery.DataSetLineageServiceTest
org.apache.atlas.service.DefaultMetadataServiceTest
org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
org.apache.atlas.repository.typestore.StoreBackedTypeCacheProviderTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.discovery.DataSetLineageServiceTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.service.DefaultMetadataServiceTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Test results:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/301//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/301//console
This message is automatically generated.
> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
> Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: rb48565.patch
>
>
> A modified version of the default local cache provider which will run a
> lookup on the backend storage if a requested type is not found in the cache,
> and load it in the cache and return it if it's found. This lazy-loading cache
> would cover the case where new types are registered, not the case where
> existing types are modified, while avoiding the deployment/maintenance and
> performance impact of a distributed cache in an HA environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
