[
https://issues.apache.org/jira/browse/TIKA-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109026#comment-18109026
]
Hudson commented on TIKA-4848:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk17 #1588 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1588/])
TIKA-4848: FileSystemEmitter writes to a tmp file and renames atomica… (#3085)
(github:
[https://github.com/apache/tika/commit/6a2cad3f4958add3db4b0f52136e8c6400f51bbf])
* (edit) CHANGES.txt
* (edit) docs/modules/ROOT/pages/pipes/plugins/filesystem.adoc
* (edit)
tika-pipes/tika-pipes-plugins/tika-pipes-file-system/src/main/java/org/apache/tika/pipes/emitter/fs/FileSystemEmitterConfig.java
* (edit)
tika-pipes/tika-pipes-plugins/tika-pipes-file-system/src/test/java/org/apache/tika/pipes/emitter/fs/FileSystemEmitterTest.java
* (edit)
tika-pipes/tika-pipes-plugins/tika-pipes-file-system/src/main/java/org/apache/tika/pipes/emitter/fs/FileSystemEmitter.java
> Enable redaction of exception messages and/or full stack traces
> ---------------------------------------------------------------
>
> Key: TIKA-4848
> URL: https://issues.apache.org/jira/browse/TIKA-4848
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> Exception messages can sometimes include confidential information.
> In 3.x, we had stacktrace on/off in tika-server, but then we included the
> full stacktrace for embedded files.
> We should have one policy throughout the parse life cycle, including in
> tika-server.
> I propose three options:
> 1) Full stacktrace (as we have now)
> 2) Redacted message, but the rest of the stacktrace
> 3) Fully redacted stacktrace (maybe just the class).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
