[
https://issues.apache.org/jira/browse/SLING-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870160#comment-16870160
]
Carsten Ziegeler commented on SLING-8523:
-----------------------------------------
[~ashokpanghal] My assumptions in the previous comment were wrong, an example
ID is:
{noformat}
org.apache.sling.featureflags.Feature.org.apache.sling.featureflags.Feature.25b26eb7-8889-4a57-9a8b-072ad160ea36
{noformat}
So we have the factory pid "org.apache.sling.featureflags.Feature" twice,
followed by the name "org.apache.sling.featureflags.Feature"
Looking at your patch again, I think it is correct; I added some comments to it.
In addition, a test would be needed
I think we could also do a clean up if this situation is detected and delete a
potential dupliate configuration
> Duplicate OSGI configs after upgrade
> ------------------------------------
>
> Key: SLING-8523
> URL: https://issues.apache.org/jira/browse/SLING-8523
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Reporter: Ashok Kumar
> Priority: Critical
> Attachments: image-2019-06-20-15-29-56-200.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> upgrade is resulting in duplicate factory configurations (configuration with
> .PID versus ~PID format) files which affect the configs related
> functionality. It happens for odd cases where alias comes as null.
> Linked issue - SLING-7786
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
