+1 to everything below. My biggest near term goal is 1.7 and we need an answer to integration + metadata on that.
Then I think we can address the TODOs including back incompat ones potentially for 2.0. Cheers Tim. Cheers, Chris ------------------------ Chris Mattmann [email protected] -----Original Message----- From: "Allison, Timothy B." <[email protected]> Reply-To: <[email protected]> Date: Thursday, December 18, 2014 at 7:51 AM To: "[email protected]" <[email protected]> Subject: Tika 2.0??? >I feel Tika 2.0 coming up soon (well, April-ish?!) and the breaking of >some other areas of back compat, esp. parser class loading -> config ... > >What other areas for breaking or revamping do others see for 2.0? > >We need a short-term fix to get the tesseract ocr integration+metadata >out the door with 1.7, of course. > > >-----Original Message----- >From: Chris Mattmann [mailto:[email protected]] >Sent: Thursday, December 18, 2014 10:42 AM >To: [email protected] >Subject: Re: Outputting JSON from tika-server/meta > >Yeah I think we should probably combine them..and make >JSON the default (which unfortunately would break back >compat, but in my mind would make a lot more sense) > >------------------------ >Chris Mattmann >[email protected] > > > > >-----Original Message----- >From: "Allison, Timothy B." <[email protected]> >Reply-To: <[email protected]> >Date: Thursday, December 18, 2014 at 7:20 AM >To: "[email protected]" <[email protected]> >Subject: RE: Outputting JSON from tika-server/meta > >>Do you have any luck if you call /metadata instead of /meta? >> >>That should trigger MetadataEP which will return Json, no? >> >>I'm not sure why we have both handlers, but we do... >> >> >>-----Original Message----- >>From: Sergey Beryozkin [mailto:[email protected]] >>Sent: Thursday, December 18, 2014 9:56 AM >>To: [email protected] >>Subject: Re: Outputting JSON from tika-server/meta >> >>Hi Peter >>Thanks, you are too nice, it is a minor bug :-) >>Cheers, Sergey >>On 18/12/14 14:50, Peter Bowyer wrote: >>> Thanks Sergey, I have opened TIKA-1497 for this enhancement. >>> >>> Best wishes, >>> Peter >>> >>> On 18 December 2014 at 14:31, Sergey Beryozkin <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi, >>> I see MetadataResource returning StreamingOutput and it has >>> @Produces(text/csv) only. As such this MBW has no effect at the >>>moment. >>> >>> We can update MetadataResource to return Metadata directly if >>> application/json is requested or update MetadataResource to >>>directly >>> convert Metadata to JSON in case of JSON being accepted >>> >>> Can you please open a JIRA issue ? >>> >>> Cheers, Sergey >>> >>> >>> >>> On 18/12/14 13:58, Peter Bowyer wrote: >>> >>> Hi, >>> >>> I suspect this has a really simple answer, but it's eluding me. >>> >>> How do I get the response from >>> curl -X PUT -T /path/to/file.pdf http://localhost:9998/meta >>> to be JSON and not CSV? >>> >>> I've discovered JSONMessageBodyWriter.java >>> >>>(https://github.com/apache/__tika/blob/__af19f3ea04792cad81b428f1df9f5e_ >>>_ >>>bbb2501913/tika-server/src/__main/java/org/apache/tika/__server/JSONMess >>>a >>>geBodyWriter.__java >>> >>><https://github.com/apache/tika/blob/af19f3ea04792cad81b428f1df9f5ebbb25 >>>0 >>>1913/tika-server/src/main/java/org/apache/tika/server/JSONMessageBodyWri >>>t >>>er.java>) >>> so I think the functionality is present, tried adding --header >>> "Accept: >>> application/json" to the cURL call, in line with the >>> documentation for >>> outputting CSV, but no luck so far. >>> >>> Many thanks, >>> Peter >>> >>> >>> >>> >>> -- >>> Maple Design Ltd >>> http://www.mapledesign.co.uk >>> <http://www.mapledesign.co.uk/>+44 (0)845 123 8008 >>> >>> Reg. in England no. 05920531 >> >> > >
