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

ASF GitHub Bot commented on NIFIREG-215:
----------------------------------------

Github user bbende commented on a diff in the pull request:

    https://github.com/apache/nifi-registry/pull/149#discussion_r241191410
  
    --- Diff: 
nifi-registry-core/nifi-registry-data-model/src/main/java/org/apache/nifi/registry/bucket/Bucket.java
 ---
    @@ -41,6 +41,8 @@
     
         private String description;
     
    +    private Boolean allowExtensionBundleRedeploy;
    --- End diff --
    
    Right now the way it is implemented, SNAPSHOTS are treated special and 
always allow redeployment, so the boolean is really just for whether or not 
"released" artifacts (i.e. non-snapshot) can be redeployed.
    
    Maybe there is a better name for the field though? 
    
    I was mostly thinking of how Nexus has some kind of global checkbox that 
lets you say whether you can redeploy released artifacts to the given Nexus 
instance.


> Extension Bundle Improvements
> -----------------------------
>
>                 Key: NIFIREG-215
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-215
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>              Labels: Extension_Registry
>             Fix For: 0.4.0
>
>
> This ticket is to implement some additional improvements to the work done in 
> NIFIREG-211.
>  * Store file size of a bundle in the DB and make it available in retrieved 
> objects
>  * Provide a method to check if a bundle exists (true or false)
>  * Provide an option to allow uploading and overwriting an existing bundle
>  * Consider making snapshots a special version that can always be overridden



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

Reply via email to