Return-Path: X-Original-To: apmail-nifi-commits-archive@minotaur.apache.org Delivered-To: apmail-nifi-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2EA6817806 for ; Mon, 16 Mar 2015 21:00:01 +0000 (UTC) Received: (qmail 74325 invoked by uid 500); 16 Mar 2015 21:00:01 -0000 Delivered-To: apmail-nifi-commits-archive@nifi.apache.org Received: (qmail 74284 invoked by uid 500); 16 Mar 2015 21:00:01 -0000 Mailing-List: contact commits-help@nifi.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.incubator.apache.org Delivered-To: mailing list commits@nifi.incubator.apache.org Received: (qmail 74265 invoked by uid 99); 16 Mar 2015 21:00:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Mar 2015 21:00:01 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 16 Mar 2015 21:00:00 +0000 Received: (qmail 72213 invoked by uid 99); 16 Mar 2015 20:59:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Mar 2015 20:59:39 +0000 Date: Mon, 16 Mar 2015 20:59:39 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: commits@nifi.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-353) Create a Data Viewer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/NIFI-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363930#comment-14363930 ] ASF subversion and git services commented on NIFI-353: ------------------------------------------------------ Commit 1a05c9db63cbbe21e08b40a87da14526653c41e1 in incubator-nifi's branch refs/heads/NIFI-353 from [~joewitt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=1a05c9d ] NIFI-353 merged to latest dev post 002 release and fixed pom references. Viewer looks great > 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)