tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TIKA-2287) Allow general jdbc connectivity for tika-eval
Date Fri, 03 Mar 2017 13:49:45 GMT

     [ https://issues.apache.org/jira/browse/TIKA-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tim Allison resolved TIKA-2287.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.15
                   2.0

Tested with derby in memory and postgresql.  

Given the complexity of the SQL used in the reports, we can only support H2 for the default
reports.  However, if an advanced user wants to modify that sql for their own db's sql syntax,
s/he can now connect Profile, Compare and Report to jdbc.

If anyone has any problems with the SQL in Profile and Compare, we should try to fix that.
 However, all bets are off with Report. 

> 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)

Mime
View raw message