nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MINIFI-482) MiNiFi handle multiple NiFi urls in RPG
Date Wed, 05 Dec 2018 19:51:00 GMT

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

ASF GitHub Bot commented on MINIFI-482:
---------------------------------------

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

    https://github.com/apache/nifi-minifi/pull/148#discussion_r239213358
  
    --- Diff: minifi-commons/minifi-commons-schema/src/main/java/org/apache/nifi/minifi/commons/schema/RemoteProcessGroupSchema.java
---
    @@ -151,7 +152,7 @@ public String getComment() {
             return comment;
         }
     
    -    public String getUrl() {
    +    public String getUrls() {
             return url;
    --- End diff --
    
    Super minor and I honestly didn't look too close to see if it makes sense, but would it
be beneficial at all to rename `url` to `urls`, too?


> MiNiFi handle multiple NiFi urls in RPG
> ---------------------------------------
>
>                 Key: MINIFI-482
>                 URL: https://issues.apache.org/jira/browse/MINIFI-482
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>            Reporter: Neha Bathra
>            Assignee: Aldrin Piri
>            Priority: Critical
>
> For an RPG, when multiple comma separated nifi urls are configured, only the first url
is considered for data flow. In case,  the first url is down, it should be tried on the
other nodes. Currently, the data flow gets stuck when the first nifi url is down.



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

Mime
View raw message