[
https://issues.apache.org/jira/browse/TIKA-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3782.
-------------------------------
Fix Version/s: 2.4.1
Resolution: Fixed
> 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)