[jira] [Commented] (TIKA-1332) Create tika-eval module

2017-02-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871033#comment-15871033 ] Hudson commented on TIKA-1332: -- SUCCESS: Integrated in Jenkins build tika-2.x #218 (See

[jira] [Commented] (TIKA-1332) Create tika-eval module

2017-02-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871034#comment-15871034 ] Hudson commented on TIKA-1332: -- SUCCESS: Integrated in Jenkins build Tika-trunk #1202 (See

[jira] [Commented] (TIKA-1332) Create tika-eval module

2017-02-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870748#comment-15870748 ] Hudson commented on TIKA-1332: -- SUCCESS: Integrated in Jenkins build Tika-trunk #1201 (See

Re: Move oldest release archive from lucene/tika to tika?

2017-02-16 Thread Chris Mattmann
Hey Jan, Yeah I guess the motivation to me is not just for people to know that they exist, but in general to follow Apache release policy in terms of making releases immutable, in a persistent location, and so forth. What do others think? I don’t feel strongly either way. I’m happy to copy the

tika-2.x - Build # 216 - Still Failing

2017-02-16 Thread Apache Jenkins Server
The Apache Jenkins build system has built tika-2.x (build #216) Status: Still Failing Check console output at https://builds.apache.org/job/tika-2.x/216/ to view the results.

[jira] [Commented] (TIKA-1332) Create tika-eval module

2017-02-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870576#comment-15870576 ] Hudson commented on TIKA-1332: -- FAILURE: Integrated in Jenkins build tika-2.x #216 (See

[jira] [Commented] (TIKA-1332) Create tika-eval module

2017-02-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870492#comment-15870492 ] Hudson commented on TIKA-1332: -- SUCCESS: Integrated in Jenkins build Tika-trunk #1199 (See

[jira] [Commented] (TIKA-1332) Create tika-eval module

2017-02-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870441#comment-15870441 ] Hudson commented on TIKA-1332: -- FAILURE: Integrated in Jenkins build tika-2.x #215 (See

tika-2.x - Build # 215 - Failure

2017-02-16 Thread Apache Jenkins Server
The Apache Jenkins build system has built tika-2.x (build #215) Status: Failure Check console output at https://builds.apache.org/job/tika-2.x/215/ to view the results.

[jira] [Updated] (TIKA-1332) Create tika-eval module

2017-02-16 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-1332: -- Summary: Create tika-eval module (was: Create "eval" code) > Create tika-eval module >

[jira] [Commented] (TIKA-1332) Create "eval" code

2017-02-16 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870408#comment-15870408 ] Tim Allison commented on TIKA-1332: --- Thank you for the feedback. I agree. Lucene is now downgraded to

[jira] [Commented] (TIKA-1332) Create "eval" code

2017-02-16 Thread Nick Burch (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870398#comment-15870398 ] Nick Burch commented on TIKA-1332: -- Unless we really need a Lucene 6 feature, for now to avoid surprises /

[jira] [Commented] (TIKA-1332) Create "eval" code

2017-02-16 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870392#comment-15870392 ] Tim Allison commented on TIKA-1332: --- Rolled back to Lucene 5.5.3 for now. > Create "eval" code >

[jira] [Reopened] (TIKA-1332) Create "eval" code

2017-02-16 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison reopened TIKA-1332: --- Ha. So, Lucene requires Java 8. Any preference for a) rolling back to Lucene 5.x which requires Java 7

[jira] [Commented] (TIKA-1332) Create "eval" code

2017-02-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870351#comment-15870351 ] Hudson commented on TIKA-1332: -- UNSTABLE: Integrated in Jenkins build Tika-trunk #1198 (See

[jira] [Updated] (TIKA-2267) Add common tokens files for tika-eval

2017-02-16 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-2267: -- Summary: Add common tokens files for tika-eval (was: Add commontokens files for tika-eval) > Add

[jira] [Created] (TIKA-2267) Add commontokens files for tika-eval

2017-02-16 Thread Tim Allison (JIRA)
Tim Allison created TIKA-2267: - Summary: Add commontokens files for tika-eval Key: TIKA-2267 URL: https://issues.apache.org/jira/browse/TIKA-2267 Project: Tika Issue Type: Improvement

[jira] [Resolved] (TIKA-1332) Create "eval" code

2017-02-16 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-1332. --- Resolution: Fixed Assignee: Tim Allison Fix Version/s: 1.15 2.0

[jira] [Commented] (TIKA-1332) Create "eval" code

2017-02-16 Thread Tim Allison (JIRA)
[ https://issues.apache.org/jira/browse/TIKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870321#comment-15870321 ] Tim Allison commented on TIKA-1332: --- Thank you, [~gagravarr]! > Create "eval" code > --

RE: Testing an ingest framework that uses Apache Tika

2017-02-16 Thread Allison, Timothy B.
Thank you, Chris, Luís and Konstantin! -Original Message- From: Mattmann, Chris A (3010) [mailto:chris.a.mattm...@jpl.nasa.gov] Sent: Thursday, February 16, 2017 10:18 AM To: dev@tika.apache.org; lfcnas...@gmail.com Cc: solr-u...@lucene.apache.org Subject: Re: Testing an ingest

Re: Testing an ingest framework that uses Apache Tika

2017-02-16 Thread Mattmann, Chris A (3010)
++1 awesome job ++ Chris Mattmann, Ph.D. Principal Data Scientist, Engineering Administrative Office (3010) Manager, NSF & Open Source Projects Formulation and Development Offices (8212) NASA Jet Propulsion Laboratory

Re: Move oldest release archive from lucene/tika to tika?

2017-02-16 Thread Jan Høydahl
Just trying to understand why we need to have hadoop, nutch, tika and mahout releases lying aorund when nobody will come to Lucene for them anymore, and I doubt anyone would prefer to use those versions. So no pressing “need”, just general housekeeping. Both Hadoop and Mahout projects have

Re: Testing an ingest framework that uses Apache Tika

2017-02-16 Thread Luís Filipe Nassif
Excellent, Tim! Thank you for all your great work on Apache Tika! 2017-02-16 11:23 GMT-02:00 Konstantin Gribov : > Tim, > > it's a awesome feature for downstream projects' integration tests. Thanks > for implementing it! > > чт, 16 февр. 2017 г. в 16:17, Allison, Timothy B.

Re: Testing an ingest framework that uses Apache Tika

2017-02-16 Thread Konstantin Gribov
Tim, it's a awesome feature for downstream projects' integration tests. Thanks for implementing it! чт, 16 февр. 2017 г. в 16:17, Allison, Timothy B. : > All, > > I finally got around to documenting Apache Tika's MockParser[1]. As of > Tika 1.15 (unreleased), add

Testing an ingest framework that uses Apache Tika

2017-02-16 Thread Allison, Timothy B.
All, I finally got around to documenting Apache Tika's MockParser[1]. As of Tika 1.15 (unreleased), add tika-core-tests.jar to your class path, and you can simulate: 1. Regular catchable exceptions 2. OOMs 3. Permanent hangs This will allow you to determine if your ingest framework is robust