You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2019/06/11 11:52:00 UTC

[jira] [Commented] (SLING-8481) Caching of Feature Model Analyser Metadata

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

Carsten Ziegeler commented on SLING-8481:
-----------------------------------------

a) is already handled by  SLING-8474
b) I don't like the idea of a sidecar, the feature model provides extensions and an extension can be used for this. This is one of the use cases/requirements we had in the initial design of the feature model.

> Caching of Feature Model Analyser Metadata
> ------------------------------------------
>
>                 Key: SLING-8481
>                 URL: https://issues.apache.org/jira/browse/SLING-8481
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>            Reporter: Dominik Süß
>            Priority: Major
>
> The feature model analyser is currently acting on the information of the feature model files as well as the metadata of artifacts. While feature models have a small footprint the extraction of the metadata from binaries is costly.
> Caching of this metadata should be improved in 2 ways:
> a) metadata should only be extracted once and be cached in process to avoid repetitive reading of binaries to access the same metadta
> b) it should be possible to store a "sidecar" artifact to a feature model to contain the extracted metadata from the binaries it references to eliminate the need for full binaries to be parsed or potentially even to have to be present for the analyser to run.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)