nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-353) Create a Data Viewer
Date Mon, 09 Mar 2015 02:57:38 GMT

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

ASF subversion and git services commented on NIFI-353:
------------------------------------------------------

Commit ee28e9de729dad477cc97b46d9a5e9cd9ef84609 in incubator-nifi's branch refs/heads/NIFI-353
from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=ee28e9d ]

NIFI-353:
- Replacing dependency on tika parsers with icu4j.

> 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
>
> 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)

Mime
View raw message