Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DC213200C78 for ; Thu, 18 May 2017 16:24:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DA87B160BC4; Thu, 18 May 2017 14:24:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 371A8160BA7 for ; Thu, 18 May 2017 16:24:09 +0200 (CEST) Received: (qmail 15427 invoked by uid 500); 18 May 2017 14:24:08 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 15416 invoked by uid 99); 18 May 2017 14:24:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2017 14:24:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 06437C061B for ; Thu, 18 May 2017 14:24:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ilZYu2qYHdHN for ; Thu, 18 May 2017 14:24:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id DE4065FDB6 for ; Thu, 18 May 2017 14:24:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0D61CE0D77 for ; Thu, 18 May 2017 14:24:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 617B4263AB for ; Thu, 18 May 2017 14:24:04 +0000 (UTC) Date: Thu, 18 May 2017 14:24:04 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1428) Allow tika config parameter MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 18 May 2017 14:24:10 -0000 [ https://issues.apache.org/jira/browse/CONNECTORS-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015821#comment-16015821 ] Karl Wright commented on CONNECTORS-1428: ----------------------------------------- Hi Julien, It's not a good idea to configure connectors in MCF from files, especially since this makes little sense in a clustered environment. If you want configurability, what we'd need to do is add a list of name/value pairs to either the Configuration or Specification UI's for the connector. There are a number of these widgets around in other connectors, so it should be straightforward to port one of those to the proper place in the Tika connectors. Is this something you'd like to provide a patch for? > Allow tika config parameter > --------------------------- > > Key: CONNECTORS-1428 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1428 > Project: ManifoldCF > Issue Type: Wish > Components: Tika extractor > Affects Versions: ManifoldCF 2.7 > Reporter: Julien Massiera > Assignee: Karl Wright > Priority: Minor > > It would be nice to have an option to pass a tika config file to the connector through the UI. > The connector would load it in the "TikaParser" class like : > private static Parser parser = new AutoDetectParser(new TikaConfig(new File("path/to/file"))); > This is just an example of course, it has to be done properly -- This message was sent by Atlassian JIRA (v6.3.15#6346)