Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
User-Agent: Microsoft-MacOutlook/f.1b.0.161010
Date: Sun, 22 Jan 2017 20:49:09 -0800
Subject: Re: Apache Tika Component
From: Chris Mattmann <mattmann@apache.org>
To: <dev@camel.apache.org>
Message-ID: <8DE2629C-7F89-4385-8D49-3EEBD12466CE@gmail.com>
Thread-Topic: Apache Tika Component
References: <de016b0f-ef01-d265-b746-ab30731f2584@apache.org>
In-Reply-To: <de016b0f-ef01-d265-b746-ab30731f2584@apache.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable
archived-at: Mon, 23 Jan 2017 04:48:07 -0000

Great job, Bob! =E2=98=BA


On 1/22/17, 8:17 PM, "Bob Paulin" <bob@apache.org> wrote:

    Hi,
   =20
    I'd like to propose an Apache Tika[1] connector for Apache Camel.  I se=
e
    Camel uses a number of Tika components like PDFBox but it could be
    interesting to have a full assortment of file parsers to convert files
    to text.
   =20
    The basic configuration would allow MIME type detection and parsing
    files to text.=20
   =20
    tika:detect
   =20
    File/Inputstream -> camel-tika -> MIME Type
   =20
    tika:parse
   =20
    File/Inputstream ->  camel-tika -> OutputStream in text
   =20
    I have a basic implementation that I'd be happy to send in a PR but I
    wanted to see if this was something the community was interested in.  I
    think it might be interesting to combine a project that integrates
    everything with the project the parses everything.  I also think having
    a camel-tika component might help achieve some of Tika's 2.0 goals.
   =20
   =20
    - Bob Paulin
   =20
   =20
    [1] https://tika.apache.org/
   =20
    [2] https://wiki.apache.org/tika/Tika2_0RoadMap
   =20
   =20
   =20