t; connection handle on top of layer one. A user needs to at least know which
> one of these the double click is targeted against and aim accordingly.
>
> On Fri, Nov 13, 2015 at 12:33 PM, Matt Gilman <matt.c.gil...@gmail.com>
> wrote:
>
>> I'm not against the double click
Chakri,
I can provide some background about using NiFi behind a proxy. There are a
couple of key items to know when doing this.
1) NiFi is comprised of a number of web applications (web ui, web api,
documentation, custom ui's, etc). So you'll need to set up your mapping to
the root path. That
Devin,
Within the config you need specify "properties".
{
"revision": {
"version": 0,
"lastModifier": "value"
},
"processor": {
"config": {
"properties": {
"Consumer Secret": "xxx",
"Access Token Secret": "xxx"
Chakri,
Looks like your running in clustered mode. It appears to have entered into
safe mode which is preventing any change requests. Safe mode happens when
your primary is disconnected. If you go to your Cluster table (through the
icon in the upper right hand side), you can rejoin that node to
Chris,
Can you please elaborate? What do you mean by the page stops working?
Thanks!
Matt
On Fri, Sep 25, 2015 at 5:57 AM, Chris Teoh wrote:
> We have had other users encounter another issue where the page displaying
> the flows stop working. How do they recover from
gt; My ultimate goal is to put all of this data into a Confluent Kafka topic,
>> taking advantage of the schema registry. I do not believe the current
>> PutToKafka provides the ability to use this registry correct? I’m curious
>> if anyone is working on PutToConfluentKafka pro
Chakrader,
I was able to upload using curl with the follow command.
curl -X POST -v -F template=@"/path/to/template.xml" http://
{host}:{port}/nifi-api/controller/templates
The endpoint that accepts the template upload accepts multipart/form-data
which I believe is the default when using curl
John,
The feature you're describing is our multi-tenant dataflow [1]. We are
currently still in the planning stages though we should have some mockups
that we will post in the coming weeks.
Currently, to support your use case, each student would need to install
NiFi in their $HOME directory.
Mike,
Yes. Master branch is undergoing significant work in preparation for 1.0.0.
That specific issue was addressed yesterday but the fix had not been merged in
yet. Please stick to our stable 0.x branch as we continue this working towards
1.0.0.
Thanks.
Matt
Sent from my iPhone
> On Jun
Mike,
Just wanted to follow up that the specific issue you mentioned has been
merged into master. Feel free to check out master and track our progress
towards progress towards that release.
Thanks.
Matt
On Thu, Jun 2, 2016 at 6:17 AM, Matt Gilman <matt.c.gil...@gmail.com> wrote:
Philippe,
You have a couple options.
1) You could write a Reporting Task that does this. We already offer a
Reporting Task that takes this stats and writes them to a log file [1].
2) You could use the REST API to get the status. The endpoint in question
would be
Thanks for reporting this. The issue is specifically tied to downloading
resources (content or templates) and accessing UI extensions (like the
content viewer or custom UI) when logged in via LDAP. Using client
certificates should be working as expected.
This token issue is addressed in NIFI-1497
eer
> Conrad
>
> From: Matt Gilman <matt.c.gil...@gmail.com>
> Reply-To: "users@nifi.apache.org" <users@nifi.apache.org>
> Date: Monday, 22 February 2016 at 15:04
> To: "users@nifi.apache.org" <users@nifi.apache.org>
> Subject: Re:
at 11:58 AM, Matt Gilman <matt.c.gil...@gmail.com>
wrote:
> Philippe,
>
> NiFi employs an optimistic locking scheme that requires clients to pass in
> a revision when making a mutable request. The revision is comprised of a
> version (a number that increments with each modif
Philippe,
NiFi employs an optimistic locking scheme that requires clients to pass in
a revision when making a mutable request. The revision is comprised of a
version (a number that increments with each modification) and a client id.
The client id can be any string. Typically however, you'll use
When NiFi is running over HTTP everyone accesses the application as an
anonymous user and has full access.
If you want to have individual user accounts, you'll need to first run NiFi
over HTTPS. In order to do this, you'll need to obtain a server certificate
for NiFi to use. These details are
Michail,
Just so I understand what's not working, can you explain the behavior
you're seeing? Does the UI not load at all? Does the UI load but your
unable to make subsequent changes?
Thanks!
Matt
On Mon, Mar 14, 2016 at 10:56 AM, michail salichos <
michail.salic...@gmail.com> wrote:
> I
.salic...@gmail.com> wrote:
> Hello,
>
> Please find attached a screenshot.
>
> As you might see, it loads the page but missing all subsequent requests.
>
> To answer your question I am still far from reaching the canvas!
>
> Regards,
> Michail
>
> On Tue, Mar
Sudeep,
The database repository holds details on the users for this NiFi and the
history of flow configuration changes. For the users, it holds last access
time, last verified time (when their authorities were last checked), a
cache of their authorities, account status, and their signing key
Dmitry,
/controller/templates
Will return all the templates that have been created/imported in your NiFi
instance. Created/Imported in this case does not mean instantiated in your
data flow on the canvas. It's just the definition of the template that has
been defined. Each template will have an
Uwe,
It's the same port however it's a different context path. Specifically, it's
available at /nifi-api instead of /nifi. The documentation is available in the
NiFi docs by scrolling to the developer section on the left hand side. Let me
know if you have any other questions.
Matt
Sent from
6 Feb 29 10:31 .
> drwxr-xr-x. 132 russ russ 12288 Feb 29 10:31 ..
> -rw-r--r--. 1 russ russ 1183 Feb 29 10:31 index.html
>
>
> On 03/07/2016 02:45 PM, Matt Gilman wrote:
>
> Russell,
>
> It doesn't appear that your Processor is appearing in the documentation at
>
Hi,
Thanks for writing in. The master branch is undergoing substantial work in
preparation for our 1.0.0 release. I would recommend working off the 0.x branch
(which is still being released regularly) until development on master settles
down. Thanks.
Matt
Sent from my iPhone
> On May 15,
Keith,
Were there any errors in any of the log's (nifi-app.log or nifi-user.log)
before shutdown or during start up. I'm not 100% sure what version your
running but it appears it's having trouble loading the Anonymous user. This
user is created during startup, stored in the users database, and
Igor,
You have a couple options.
1) You could write a Reporting Task that does this. We already offer a
Reporting Task that logs component status to a log file [1].
2) You could use the REST API to get the status. The endpoint in question
would be
If you check the nifi-users.log there should be a message that contains
details of the field that it was unable to unmarshal. The documentation
does appear to indicate that every field is optional. I've updated this
JIRA [1] to address the documentation for our upcoming release.
Matt
[1]
gt; Matt Clarke: The permissions look fine. Nifi runs as user “nifi” and all
> files are owned by “nifi” (with write permissions of course)
>
> Matt Gilman:
> As far as additional logging here is what I found – No errors of any sort:
>
> 016-07-25 16:10:59,420 INFO [main]
> o.a.
nformation I provided in the entity could not be
> posted. What could be the issue?
>
> Mariama Barr-Dallas
> Meyerhoff Scholar/ NSA Scholar M23
> Computer Science Major, History Major
> University of Maryland Baltimore County
> Class of 2015
>
> On Fri, Jul 22, 2016 a
Nawaz,
Can you double check how you're attempting to set the relationship to
auto-terminate? There is a flag which is part of the Relationship that is
considered read-only and reports the current state of the relationship.
However, to auto-terminate a connection you need to add it to the
Ralph,
Based on the details in your email, it sounds like it should be working. At
start up, it will go through the users database to re-verify each user with
the configured provider. The authorizations for a user are cache in this
database for a configurable time. The re-verification is done to
er -X (nakther - INSIGHT GLOBAL
> INC at Cisco) <nakt...@cisco.com> wrote:
>
>> That worked! Thanks Matt.
>>
>>
>>
>> Nawaz.
>>
>>
>>
>> *From:* Matt Gilman [mailto:matt.c.gil...@gmail.com]
>> *Sent:* Thursday, July 28,
Joe,
Can you provide any more details? The logs/nifi-user.log should be logging each
request. Are they any additional details in there?
Matt
Sent from my iPhone
> On Jul 1, 2016, at 5:43 PM, Joe Skora wrote:
>
> Ok, that was a certificate hostname problem.
>
> Now, when I
BH,
You should be able to select the components in question and dragging and
dropping them into the desired Process Group. You can select the components
by holding down Shift and clicking on each one. Another option is to use a
selection box by clicking and dragging on the canvas. You should see
Just wanted to add to Bryan's response that there is a JIRA [1] that
captures the ability to synchronize LDAP user/groups. This is probably a
good place to capture any additional use cases.
Matt
[1] https://issues.apache.org/jira/browse/NIFI-3409
On Sun, Jan 29, 2017 at 6:25 PM, Bryan Bende
I'm not super familiar with this endpoint so hopefully someone else can
chime in here if necessary. But I believe the transactionId is already
composed in the Location header of this endpoint
POST
/data-transfer/input-ports/{portId}/transactions
There is a Java class [1] available in NiFi
A couple comments. Apache NiFi is comprised of a number of web
applications. You've mapped to three of them. However, we also support UI
extensions for Custom Processor configuration (like UpdateAttribute and
JoltTransformJson) and custom data viewers (based on content type) when
looking at data
i
> is asking for JWT.
> Please, Could anyone share your Apache HTTPd Proxy configuration ?
>
> Regards.
>
> - wr
>
>
>
> On 16 January 2017 at 14:38, Matt Gilman <matt.c.gil...@gmail.com> wrote:
>
>> A couple comments. Apache NiFi is comprised of a number of web
Peter,
Thanks for checking in regarding this issue. I believe what you're seeing
has been addressed [1] on master since the BETA was cut a few weeks ago.
Feel free to give it a shot in your most recent build with auth enabled and
let us know if you're still seeing weirdness.
Thanks!
Matt
[1]
Nick,
In 1.0.0 we've moved away from role based authorities in favor of fine
grain access controls with a delegated authorizer. Whether an anonymous
user is authorized would be a function of the configured authorizer. The
authorizer is given details about the users request and it will make an
Andre,
Which version of Apache NiFi are you using?
In 0.x authorities are defined using the string that is returned from the
authenticator so there should be no issue here.
In 1.x users are entered by hand either through the UI or in the
authorizers.xml file (for the initial admin). This value
vironment I was testing on seemed quite weird, hence the reason I
> asked if anyone else seen that while integrating into AD LDS (I don't have
> many of those available to test).
>
> Also, I away from the box at the moment but I recall leaving
> nifi.security.identity.mapping unchanged (IIR
not possible
> in 1.0.0 and the update to accommodate this configuration is forthcoming in a
> future release.
>
> -Nick
>
>
>> On Sun, Sep 4, 2016 at 12:18 AM, Matt Gilman <matt.c.gil...@gmail.com> wrote:
>> Nick,
>>
>> In 1.0.0 we've moved awa
Peter,
What is the processor downstream of the connection in question? Thanks.
Matt
On Fri, Sep 9, 2016 at 10:39 AM, Matt Gilman <matt.c.gil...@gmail.com>
wrote:
> Peter,
>
> Thanks for the answers. Still not quite sure what's causing this and am
> trying to narrow down
and deleted the
>> authorizations.xml file , I now get the following exception on the
>>
>>
>> Proposed Authorizer is not inheritable by the flow controller because
>> of Authorizer differences: Proposed Authorizations do not match current
>> Authorizations
&
Gard,
In your conf/authorizers.xml configuration file you'll see entries which
need to be populated with the nodes in your cluster. With zero master
clustering, the nodes in the cluster may be replicating requests to the
other nodes in the cluster. In order for the node to trust the end user,
gt;
>
>
> *From:* Matt Gilman [mailto:matt.c.gil...@gmail.com]
> *Sent:* Friday, September 09, 2016 8:51 AM
>
> *To:* users@nifi.apache.org
> *Subject:* Re: Erroneous Queue has No FlowFiles message
>
>
>
> Peter,
>
>
>
> What is the processor downstream of the
Downloading and viewing should be the same permissions. If you're seeing
otherwise please file a JIRA with the details. Is the instance clustered,
what permissions to you have set on the source component, etc?
Andre,
The 'view the data' is the correct policy that you need to configure. Is
your
tion that
> this was an issue caused by a bad merge on our part and wasn’t paying it
> much attention. I have not submitted a JIRA ticket.
>
>
>
> We are not clustered, running Kerberos for authentication.
>
>
>
> Thanks,
>
> Peter
>
>
>
>
>
> *From
Selvam,
The specific endpoint is
http://{host}:{port}/nifi-api/flow/cluster/summary
This will return a ClusterSummaryDTO [1] (this is incorrect in the
documentation). I'm having trouble accessing JIRA right now but we'll get
that fixed in the next release.
Matt
[1]
Nicolas,
Peter is correct. IE is not a supported browser. We do support Edge which
was introduced with Windows 10.
Thanks.
Matt
On Thu, Sep 22, 2016 at 8:20 AM, Peter Wicks (pwicks)
wrote:
> Nicolas,
>
>
>
> According to the NiFi users guide
>
Deepak,
The project website contains the documentation from the most recently
released version of Apache NiFi. The PutIgniteCache processor appears to be
introduced in the 1.x baseline so it will not show up on the website until
1.0.0 is formally released.
However, the documentation is available
Peter,
Sorry for the inconvenience. Unfortunately, the issue you're running into
is a known issue in the 1.0.0 release [1]. Are you possibly in a position
to run a SNAPSHOT build based off the current state of master. This should
have the patch incorporated. Alternatively, the 1.1.0 release
Sebastian,
It appears the jolt library is being bundled into the WAR for that
Processor's Advanced UI. Despite the UI not working with your changes, the
Process should likely run ok.
To fix the Advanced UI, you could simply bump the version there too [1] or
you could define that dependency in
t json body to send
> in the POST call .
>
> if you can give an example again
>
>
>
> Philippe
>
> Best regards
>
>
> *-----*
>
> Thanks a lot Matt
>
> It works nicely !
>
>
>
>
&g
t;
> Hello Matt, I have the same problem with the provenance/lineage REST call
>
>
>
> curl 'http://localhost:8080/nifi-api/provenance/lineage/..
>
>
>
> very difficult for me (sorry L ) to find the right json body to send
> in the POST call .
>
> if you can give an ex
Russ,
There is no way to change the background color. You'd have to fork the
codebase and update the style for the canvas-container. I believe
previously this was implemented with a repeating background image and is
now implemented with CSS. I also thought the change was subtle.
There has been
Philippe,
Yes, you are correct. These are the endpoints to access flowfile content
before and after a given provenance event. Specifically, these map to the
View/Download buttons in the Content tab for the Input and Output Claim in
the provenance event details dialog.
Matt
On Tue, Nov 15, 2016
Philippe,
Here's an example command for initiating a provenance search:
curl 'http://localhost:8080/nifi-api/provenance' -H 'Content-Type:
application/json' -H 'Accept: application/json, text/javascript, */*;
q=0.01' --data-binary
a Compressor processor hooked up on both ends.
>
>
>
> *From:* Matt Gilman [mailto:matt.c.gil...@gmail.com]
> *Sent:* Friday, November 11, 2016 12:39 PM
> *To:* users@nifi.apache.org
> *Subject:* Re: Enable Compression on Remote Port?
>
>
>
> Peter,
>
>
>
> Sor
as.
> - NiFi is not clustered.
> - DEBUG level for org.apache.nifi.web.filter.TimerFilter shows request
> duration somewhere between 2 and 20 millis.
>
> --
> Jagrut
>
> On Mon, Oct 10, 2016 at 12:26 PM, Matt Gilman <matt.c.gil...@gmail.com>
> wrote:
>
>> Jagrut,
>
Stephane,
Yes, you are correct that Apache NiFi uses swagger. However, we are only
using it for keeping the documentation in sync. We use a maven plugin that
inspects the swagger annotations and generates a swagger.json. The
swagger.json is generated to nifi-web-api/target/swagger-ui/swagger.json
In order to modify the nodes in the cluster, a user would need to have
permissions to the controller. Permissions to this resource will allow a
user to view and modify different aspects of the Flow Controller including
Reporting Tasks, Controller Services (referenced by Reporting Tasks), the
Nodes
On Wed, Dec 7, 2016 at 2:51 AM, Nirmal Kumar <nirmal.ku...@impetus.co.in>
wrote:
> Each time I fire the DELETE request I first GET the ProcessGroup details
> and then fetch the *version*.
>
> So I am passing the correct version in DELETE request.
>
>
>
> Thanks,
>
>
emplate I
> just get the stack trace as mentioned in my below mail.
>
>
>
> -Nirmal
>
>
>
> *From:* Matt Gilman [mailto:matt.c.gil...@gmail.com]
> *Sent:* Tuesday, December 6, 2016 6:58 PM
> *To:* users@nifi.apache.org
> *Subject:* Re: Getting
> org.springfram
level controller service as it was in the original NiFi instance
> before exporting the template).
>
>
> Many thanks,
>
> Panos
>
>
> --
> *From:* Matt Gilman <matt.c.gil...@gmail.com>
> *Sent:* Friday, January 13, 2017 6:27
Panos,
The current behavior is that Controller Services are only included if they
are referenced by a component in the template. While this was initially by
designed, we have received comments about it from folks looking to export
their entire configuration. There is an outstanding JIRA [1] to
Naz,
Thanks for feedback. This issue has been captured in the following JIRA
[1]. I apologize for any inconvenience.
Matt
[1] https://issues.apache.org/jira/browse/NIFI-3306
On Thu, Jan 12, 2017 at 10:22 AM, Irizarry Jr., Nazario
wrote:
> In NiFi 1.1.1 (and 1.1.0) if you pull
Alessio,
There is currently no way to lock the canvas. If the current user has
permissions to modify a given component it will be modifiable if the
component is in a valid state for the request action. For instance, if the
component is scheduled to execute it cannot be deleted.
There has been
If your instance is clustered, you'll need to authorize the nodes with the
data policies as well. Any 'data-plane' endpoint (where data or meta-data
is returned or modified) will require the nodes in the request chain to
also be approved for access as the data will traverse some of them when the
Simon,
Sorry for the late response here. I believe we encountered and addressed
this issue [1] today. Unfortunately, it just missed being included in
Apache 1.1.0 by a couple days. If you're able to build from source, this
should be fixed in the current master branch. Again sorry for the
Unfortunately, this is not configurable at the moment. You are accurate
that the bulletin is shown for 5 minutes and additionally will only retain
the last 5 bulletins per component. If the condition causing the bulletin
is recurring, you should see another bulletin generated.
The bulletins are
Nirmal,
If you consume the body of the response it should indicate the reason for
the 409. On failed responses, the response body should be text/plain. Let
me know if that helps.
Thanks
Matt
On Mon, Dec 5, 2016 at 11:29 PM, Nirmal Kumar
wrote:
> Hi All,
>
>
>
> I
e points out to me, but it might not be
> related. Kerberos returns an error:
>
>
>
> POST http://servername:1/nifi-api/access/kerberos 409
> (Conflict)
>
>
>
> Probably not related, but otherwise I do not see any other error that
> would explain what is g
t I cannot enter my new Processor Group.
>
>
>
> Strangely, my Processor Groups that do not have a GenerateFlowFile
> Processor still work. So I might have just narrowed this down to one
> Processor, GenerateFlowFile.
>
>
>
> Kevin
>
>
>
> *From:* Matt G
Sorry for the inconvenience. Is there a stack trace listed in the user log?
A quick glance at the code and the error handler looks like it logs the
exception (which should include the stack trace) unconditionally.
Also, you should be able to look backward from that line to look for other
log
I think you would need to specify every component that is on the canvas. If
all of the components were in a nested Process Group, then you would just
need to specify that Process Group.
What is the behavior you're seeing?
Thanks
Matt
On Mon, Dec 26, 2016 at 10:52 PM, prabhu Mahendran
eed rest api which create template for entire ui elements.
>
> On Tue, Jan 3, 2017 at 9:30 PM, Matt Gilman <matt.c.gil...@gmail.com>
> wrote:
>
>> I think you would need to specify every component that is on the canvas.
>> If all of the components were in a nested Pr
Pushkar,
NiFi employs an optimistic locking scheme that requires clients to pass in
a revision when making a mutable request. The revision is comprised of a
version (a number that increments with each modification) and a client id.
The client id can be any string. You should continue to use this
There is no option to add users with full privilege. Setting the initial
admin identity will give that user access to the UI and permissions to
manage users, groups, and policies. Additionally, if the NiFi instance has
an existing flow it will grant permissions to the root group. Otherwise,
the
Kumar,
Check out my response on Stack Overflow [1].
Thanks
Matt
[1]
http://stackoverflow.com/questions/42827820/how-to-pass-credential-to-nifi-rest-api
On Thu, Mar 16, 2017 at 3:33 AM, kumar r wrote:
> Hi,
>
> I have enabled LDAP authentication for Apache NiFi-1.1.1.
>
Chakri,
Unfortunately, LDAP user groups are not currently supported. Currently,
user authentication through LDAP is supported but loading/interpreting
their groups are not.
Adding the concept of a group provider which would complement the existing
identity provider seems like a good fit. Also,
Hi,
What browser are you using? We had some issues the action icons in Firefox
in NiFi 1.1.0 wrapping to the next line that is addressed in this JIRA [1].
If you are using Firefox, can you try Chrome to help narrow down the issue?
Does the policy links show up in the Controller Services tab?
Nijandan,
I can't tell how you're creating your request based off your message. I
would say to make sure you are setting the Authorization as an HTTP header
and not part of the body of the request.
Matt
On Tue, Apr 4, 2017 at 3:11 AM, Nijandan D wrote:
> Hi,
>
> I am
This is a known issue [1] that has been addressed in the upcoming 1.2.0
release. If you include a position then you should be able to creation the
component successfully. Sorry for the inconvenience.
Matt
[1] https://issues.apache.org/jira/browse/NIFI-2994
On Wed, Apr 19, 2017 at 12:00 PM,
Without knowing more of your setup, I would guess that your browser is
prompting you based on the available certificates. What happens if you
uninstall the certificate from your browser?
Matt
Sent from my iPhone
> On Mar 9, 2017, at 7:37 PM, Joe Skora wrote:
>
> I have an
mmon instances of one or more of these services typically
> shared across process groups?
>
> Regards,
> Jim
>
> On Mon, Mar 13, 2017 at 9:03 AM, Matt Gilman <matt.c.gil...@gmail.com>
> wrote:
>
>> Jim, Joe,
>>
>> Just wanted to clarify. It sounds
Jim, Joe,
Just wanted to clarify. It sounds as though your running the 0.x baseline.
In 0.x, a single revision is maintained for the entire flow. If another
user makes a change, you will get a notification that you need to Refresh
to realize their changes before you can make any changes.
In 1.x
Vijaya,
Here's a link to the contribution guide [1]. It's more oriented around
submitting a PR but should be helpful. The gist is that you'll want to run
mvn clean install
from the root directory where the NiFi source is cloned. Once that
completes the target directory of the nifi-assembly will
Matheswaran,
The Node Identities in the authorizers.xml file need to correspond with the
DN from the server certificates each node is configured with. I would
recommend using keytool to print the certificate and then copy/paste that
DN into the authorizers.xml on each node.
NOTE: A
Jennifer,
I just wanted to clarify that you can set up username/password
authentication with any directory server. It does not have to be Active
Directory. Many folks use OpenLDAP or ApacheDS depending on the
environment. As James mentioned Kerberos is also an option.
Let us know if you have any
or the response.
>
> Is there any alternate solution to achieve this?
>
> Also please look at my another stack overflow question
> https://stackoverflow.com/questions/45346902/multiple-
> initial-admin-or-initial-admin-group
>
> Thanks,
> Kumar
>
> On Wed, Jul 26, 2017
Awesome. Glad you got everything working. I've filed a JIRA for updating
the documentation accordingly [1].
Matt
[1] https://issues.apache.org/jira/browse/NIFI-4206
On Wed, Jul 19, 2017 at 8:31 AM, Raviteja Lokineni <
raviteja.lokin...@gmail.com> wrote:
> Hi all,
>
> This is what I used in
Thanks for the great summarization Andy. Just wanted to clarify one small
detail. The default file-based authorizer will use
conf/authorizations.xml though this value is configurable in
conf/authorizers.xml. In the 0.x, when NiFi used role-based authorization
the file was called
Russell,
Thanks for the suggestion on the improved Controller Service UX. Would you
mind filing a JIRA for this improvement?
In 1.x, the user can see the components referencing a Controller Service in
1 of 3 places. The references are shown in the read-only details dialog,
the service
directs public-ip/pipeline to public-ip/nifi
>
> I am stuck trying to figure out all the proxies that nifi needs. Someone
> please help me out.
>
> Thanks,
>
> On Wed, Jul 19, 2017 at 6:28 PM, Matt Gilman <matt.c.gil...@gmail.com>
> wrote:
>
>> Awesome. Glad you got eve
Tim,
Just wanted to provide a few more details. Prior to 1.2.0 the flow and
templates did not contain any details about the NAR (bundle) it was
packaged in. In 1.2.0, since your template did not contain any bundle
details NiFi attempted to find a compatible Processor (matched by class
name only).
Sorry for the delayed response. Similar behavior has been reported by some
other users [1]. Does the connection have any back pressure threshold
configured? Can new flowfiles be enqueued? Do the expiration settings have
any affect?
Lastly, if you restart the cluster does it claim the connection
gt; the queue status
> 6) I tried to change the backpressure threshold without any effect.
> 7) During the problem the queue was operating normally on the cluster, and
> flowfiles were flowing through it without any issue.
>
> Arnaud
>
>
>
> On Mon, May 15, 2017 at 10:39
Georg,
The UI will be available once you see these log messages:
2017-06-09 09:02:37,208 INFO [main] org.apache.nifi.web.server.JettyServer
NiFi has started. The UI is available at the following URLs:
2017-06-09 09:02:37,208 INFO [main] org.apache.nifi.web.server.JettyServer
http://:/nifi
NAPSHOT/logs org.apache.nifi.NiFi
> 2017-06-12 18:01:50,506 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 20304
> 2017-06-12 18:01:51,063 INFO [NiFi Bootstrap Command Listener]
> org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening
1 - 100 of 160 matches
Mail list logo