[
https://issues.apache.org/jira/browse/TIKA-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930472#comment-15930472
]
Hudson commented on TIKA-2287:
------------------------------
SUCCESS: Integrated in Jenkins build Tika-trunk #1220 (See
[https://builds.apache.org/job/Tika-trunk/1220/])
TIKA-2287 -- bug fixes (tallison:
[https://github.com/apache/tika/commit/585316d9eb41f1695429b7e374c02397531618c2])
* (edit)
tika-eval/src/main/java/org/apache/tika/eval/batch/ExtractProfilerBuilder.java
* (edit) tika-eval/src/test/java/org/apache/tika/eval/TikaEvalCLITest.java
* (edit)
tika-eval/src/main/java/org/apache/tika/eval/batch/EvalConsumersBuilder.java
* (edit) tika-eval/src/test/java/org/apache/tika/eval/ComparerBatchTest.java
* (edit)
tika-eval/src/main/java/org/apache/tika/eval/batch/EvalConsumerBuilder.java
* (edit)
tika-eval/src/main/java/org/apache/tika/eval/batch/ExtractComparerBuilder.java
> Allow general jdbc connectivity for tika-eval
> ---------------------------------------------
>
> Key: TIKA-2287
> URL: https://issues.apache.org/jira/browse/TIKA-2287
> Project: Tika
> Issue Type: Improvement
> Components: tika-eval
> Reporter: Tim Allison
> Fix For: 2.0, 1.15
>
>
> tika-eval currently uses h2 embedded. It would be useful to allow power
> users to connect to their own db via jdbc. Most of the creation/insertion
> sql is general enough. The sql that drives the reports would likely have to
> be tailored by users.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)