You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/06/03 15:09:00 UTC

[jira] [Commented] (TIKA-3782) Improve logging in pipes-iterator-jdbc

    [ https://issues.apache.org/jira/browse/TIKA-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545959#comment-17545959 ] 

Hudson commented on TIKA-3782:
------------------------------

SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #626 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/626/])
TIKA-3782 -- improve logging an idcolumn handling in jdbc pipes iterator (tallison: [https://github.com/apache/tika/commit/382c1b3996c6100b1b822e6f19061b7dae3c3131])
* (delete) tika-pipes/tika-pipes-iterators/tika-pipes-iterator-jdbc/src/test/resources/log4j.properties
* (edit) tika-pipes/tika-pipes-iterators/tika-pipes-iterator-jdbc/src/main/java/org/apache/tika/pipes/pipesiterator/jdbc/JDBCPipesIterator.java
* (add) tika-pipes/tika-pipes-iterators/tika-pipes-iterator-jdbc/src/test/resources/log4j2.xml


> Improve logging in pipes-iterator-jdbc
> --------------------------------------
>
>                 Key: TIKA-3782
>                 URL: https://issues.apache.org/jira/browse/TIKA-3782
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Priority: Trivial
>             Fix For: 2.4.1
>
>
> It is possible now to forget that an id column is needed for some use cases, for example.  We should add more logging to let the user know what has been configured and what has not been configured.
> We should add a logged backoff to use the fetchkey column for the id column if now id column is specified.  We should also allow one column to be more than one feature, e.g. one column could be fetchkey, emitkey and idkey.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)