[
https://issues.apache.org/jira/browse/TIKA-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690492#comment-17690492
]
Hudson commented on TIKA-3977:
------------------------------
FAILURE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #1027 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/1027/])
TIKA-3977 -- add postconnection sql call, clean up closing of resources and add
max retries to JDBCEmitter (#971) (github:
[https://github.com/apache/tika/commit/5e61a58096e9898a7b862bf623e68ba77206d341])
* (edit)
tika-pipes/tika-emitters/tika-emitter-jdbc/src/main/java/org/apache/tika/pipes/emitter/jdbc/JDBCEmitter.java
* (edit)
tika-pipes/tika-pipes-reporters/tika-pipes-reporter-jdbc/src/main/java/org/apache/tika/pipes/reporters/jdbc/JDBCPipesReporter.java
> JDBCEmitter and JDBCReporter should allow post connection sql call
> ------------------------------------------------------------------
>
> Key: TIKA-3977
> URL: https://issues.apache.org/jira/browse/TIKA-3977
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> Over on the developmental tika-gui-app, we're getting SQLITE_BUSY errors when
> running on a large set of files:
> https://github.com/tballison/tika-gui-v2/issues/103
> We should allow the configuration of sql calls immediately after the
> connection is made so that we can try PRAGMA busy_timeout 36000 for example.
> In reviewing the code, we should also make sure to try to close our
> connections before restarts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
