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

Tim Allison commented on TIKA-3610:
-----------------------------------

Hi [~dadoonet], at the meetup, I forgot that I already added a PipesReporter.  
See 
https://github.com/tballison/file-observatory/blob/main/tika-addons/tika-pipes-reporter/src/main/java/org/tallison/tika/pipes/TikaPipesReporter.java
 for an example of logging to issues to a jdbc endpoint. 

To invoke it, you add this element to the tika-config.xml file:

    <pipesReporter class="org.tallison.tika.pipes.TikaPipesReporter">
      <params>
        
<connectionString>jdbc:postgresql://somewhere/somedb?user=user&amp;password=password</connectionString>
      </params>
    </pipesReporter>

> Emit errors to a specific emitter
> ---------------------------------
>
>                 Key: TIKA-3610
>                 URL: https://issues.apache.org/jira/browse/TIKA-3610
>             Project: Tika
>          Issue Type: New Feature
>          Components: tika-pipes
>            Reporter: David Pilato
>            Priority: Minor
>
> Instead of emitting errors in the logs, we should emit them using an error 
> emitter instead.
> Then we can have all the flexibility we want to emit our errors to a logger, 
> to a filesystem, to whatever implementation.
> For example:
> {code:java}
> <errorEmitterName>fse</errorEmitterName> {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to