Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIFI-4499 Updated default content-viewer URL property to be relative … #2217

Closed
wants to merge 1 commit into from

Conversation

jtstorck
Copy link
Contributor

…rather than assuming it is deployed at the root context.

To test this PR:

  • Build NiFi and start it with the default nifi.properties file.
  • Configure a proxy, and point it at NiFi.
  • Access NiFi via the proxy
  • Add a processor that creates flowfiles with viewable (ie, text) data, such as GenerateFlowFile.
  • Add any other processor, such as UpdateAttribute.
  • Route the first processor to the second processor
  • Start the first processor to get some data into the outgoing queue, then stop the flow.
  • Right-click on the queue and view the queue listing
  • Select the info icon next to one of the queue items
  • From the Details tab, click View. A new tab should open with the content viewer and the flowfile data can be viewed. Close the content-viewer tab. Close the dialog with the FlowFile details.
  • From the queue listing dialog, click the Provenance icon.
  • In the Provenance frame, click the info icon for one of the events
  • Select the Content tab and click View. A new tab should open with the content viewer and the flowfile data can be viewed.
  • Shut down NiFi and the proxy.

…rather than assuming it is deployed at the root context.
@mcgilman
Copy link
Contributor

Reviewing...

@mcgilman
Copy link
Contributor

Thanks @jtstorck! This has been merged to master.

@asfgit asfgit closed this in fb839ff Oct 19, 2017
@jtstorck jtstorck deleted the NIFI-4499 branch November 13, 2017 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants