From commits-return-5745-apmail-nifi-commits-archive=nifi.apache.org@nifi.incubator.apache.org Sun Mar 15 13:17:59 2015 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 9332B106B5 for ; Sun, 15 Mar 2015 13:17:59 +0000 (UTC) Received: (qmail 66745 invoked by uid 500); 15 Mar 2015 13:17:59 -0000 Delivered-To: apmail-nifi-commits-archive@nifi.apache.org Received: (qmail 66707 invoked by uid 500); 15 Mar 2015 13:17:59 -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 66698 invoked by uid 99); 15 Mar 2015 13:17:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Mar 2015 13:17:59 +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; Sun, 15 Mar 2015 13:17:58 +0000 Received: (qmail 66390 invoked by uid 99); 15 Mar 2015 13:17:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Mar 2015 13:17:38 +0000 Date: Sun, 15 Mar 2015 13:17:38 +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=14362377#comment-14362377 ] ASF subversion and git services commented on NIFI-353: ------------------------------------------------------ Commit 73a54eeb859fe9c8822141b59ee79eba8d1e6dff in incubator-nifi's branch refs/heads/NIFI-353 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=73a54ee ] NIFI-353: - Adding support for text/plain. > 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)