[NIFI-4960] Having multiple versions of same component doesn't work as expected when using Flow Registry

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Component/s: Configuration
• Assignee: Unassigned
• Reporter: Jorge Machado
• Created: 12/Mar/18 08:36
• Updated: 12/Mar/18 13:46
• Resolved: 12/Mar/18 13:45

Description

I we setting up the Nifi registry are we are getting this error when trying to import a flow from Registry into Nifi: 

Multiple versions of …. exist. No exact match for default:...:unversioned.

To note that we have multiple versions of the same processor in the lib folder (which works for Templates)
Our Manifest inside the nar file looks like this: 
Manifest-Version: 1.0
Implementation-Title: componentName
Implementation-Version: 1.5.9.rc.1
Nar-Dependency-Group: org.apache.nifi
Nar-Version: 1.5.9.rc.1
Nar-Dependency-Version: 1.5.0
Nar-Id: componentName
Nar-Group: com.componentName
Nar-Dependency-Id: nifi-standard-services-api-nar
 
I see this on the Nifi Logs: 
2018-03-12 08:33:51,304 INFO [NiFi Web Server-94] o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: Multiple versions of com.gfk.nifi.processor.customlogging.CustomLogger exist. No exact match for default:ipmvp-nifi-customlogattribute:unversioned.. Returning Conflict response.
 
 
After some debugging I found the bug on BundleUtils and I will patch it. 

public static BundleDTO createBundleDto(final org.apache.nifi.registry.flow.Bundle bundle) {
    final BundleDTO dto = new BundleDTO();
    dto.setArtifact(bundle.getArtifact());
    dto.setGroup(dto.getGroup()); <-- Should be bundle right ? 
    dto.setVersion(dto.getVersion()); <-- should be bundle right ?
    return dto;
}

Issue Links

• links to: GitHub Pull Request #2531