[
https://issues.apache.org/jira/browse/NIFI-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375125#comment-14375125
]
Matt Gilman edited comment on NIFI-353 at 3/22/15 7:49 PM:
-----------------------------------------------------------
1) Currently there is nothing we can do about that. The plugin that we're using
to create the 'hex' view requires the input to be base 64. So when we're in
that mode, the data stream is converted to a base 64 string which is inserted
into the document being returned to the user. Pagination is good idea for a
subsequent iteration. For now I could just only show the first N bytes. Do you
know how large the file was that performed poorly?
2) Sounds like you may restarted NiFi and it came back up in between revision
requests. The browser was at revision 9 and the application was at the initial
value of 0.
3) Looks like I'm missed some error handling. Will fix that today.
4) Not sure but that doesn't sound good. When you tried to view that data again
it was good? Or this was a repeatable thing?
5) I'm a little confused what your saying here. You started with invalid JSON
that was identified as .txt and text/plain. Then the data viewer hung? Did you
get a thread dump? Can you provide an example?
6) Awesome!
The view button is only visible when the content is available and the content
viewer url has been configured in nifi.properties.
was (Author: mcgilman):
1) Currently there is nothing we can do about that. The plugin that we're using
to create the 'hex' view requires the input to be base 64. So when we're in
that mode, the data stream is converted to a base 64 string which is inserted
into the document being returned to the user. Pagination is good idea for a
subsequent iteration. For now I could just only show the first N bytes. Do you
know how large the file was that performed poorly?
2) Sounds like you may restarted NiFi and it came back up in between revision
requests. The browser was at revision 9 and the applicable was at the initial
value of 0.
3) Looks like I'm missed some error handling. Will fix that today.
4) Not sure but that doesn't sound good. When you tried to view that data again
it was good? Or this was a repeatable thing?
5) I'm a little confused what your saying here. You started with invalid JSON
that was identified as .txt and text/plain. Then the data viewer hung? Can you
provide an example?
6) Awesome!
The view button is only visible when the content is available and the content
viewer url has been configured in nifi.properties.
> Create a Data Viewer
> --------------------
>
> Key: NIFI-353
> URL: https://issues.apache.org/jira/browse/NIFI-353
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Attachments: flow_that_shows_issues_with_viewer.xml
>
>
> For use in property:
> {code}nifi.content.viewer.url{code}
> The content viewer will be extensible in that the supported mime types will
> be discovered at runtime. We will be taking an approach similar to Java SPI.
> During startup all war files will be inspected looking for a
> META-INF/nifi-data-viewer file. This file will contain the mime types that it
> can render (1 per line). Duplicate viewers will be logged and either the
> first or the last will be utilized.
> Currently, the content viewer is applicable for viewing archived data through
> the provenance UI. This will likely be expanded to integrate with other parts
> of the application where applicable (viewing content in queues, etc). When
> viewing the data, the content viewer controller will get the data stream and
> detect its type (Apache Tika, known mime type, file extension, etc). Will
> likely need to add support for decompressing/unpacking. Once the underlying
> type is known and is supported, the content viewer controller will generate
> the webpage and defer to the discovered web application to generate the mark
> up for the data (via RequestDispatcher.include). This means that the
> discovered web application does not need to generate any boilerplate HTML and
> all types of content will be viewed in a similar UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
