[
https://issues.apache.org/jira/browse/TIKA-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3941:
------------------------------
Description:
If the pipes server crashes, the only information that the pipesclient receives
is of the crash. It would be useful at a minimum to have the pipes server
report an intermediate result after file detection.
Ideally, at a minimum, the pipesclient could report file type, content-length
(if possible) and digest information.
On another ticket (future work), we could extend intermediate results to
include partial parses/metadata extraction. The challenge here is that the
underlying metadata objects are not thread safe...so we'll punt this to deal
with later if necessary.
was:
If the pipes server crashes, the only information that the pipesclient receives
is of the crash. It would be useful at a minimum to have the pipes server send
report an intermediate result after file detection.
Ideally, at a minimum, the pipesclient could report file type, content-length
(if possible) and digest information.
On another ticket (future work), we could extend intermediate results to
include partial parses/metadata extraction. The challenge here is that the
underlying metadata objects are not thread safe...so we'll punt this to deal
with later if necessary.
> Consider having pipesserver return intermediate results
> -------------------------------------------------------
>
> Key: TIKA-3941
> URL: https://issues.apache.org/jira/browse/TIKA-3941
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> If the pipes server crashes, the only information that the pipesclient
> receives is of the crash. It would be useful at a minimum to have the pipes
> server report an intermediate result after file detection.
> Ideally, at a minimum, the pipesclient could report file type, content-length
> (if possible) and digest information.
>
> On another ticket (future work), we could extend intermediate results to
> include partial parses/metadata extraction. The challenge here is that the
> underlying metadata objects are not thread safe...so we'll punt this to deal
> with later if necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
