[
https://issues.apache.org/jira/browse/TIKA-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-2662:
------------------------------
Description:
Depending on the configuration of the ForkParser, it might be useful for that
and also for tika-batch to write out each embedded file once the parse for that
embedded file has completed, rather than caching the entire output in memory.
The downside to this is that the main document will now show up at the bottom
of the list of metadata objects. We can re-arrange when we deserialize, but
anyone not using our deserialization will see this change in order. Given that
this is a breaking change, I'll make it optional.
was:
Depending on the configuration of the ForkParser, it might be useful for that
and also for tika-batch to write out each embedded file once the parse for that
embedded file has completed, rather than caching the entire output in memory.
The downside to this is that the main document will now show up at the bottom
of the list of metadata objects. We can re-arrange when we deserialize, but
anyone not using our deserialization will see this change in order.
> Add a streaming out option for the Json serialization
> -----------------------------------------------------
>
> Key: TIKA-2662
> URL: https://issues.apache.org/jira/browse/TIKA-2662
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> Depending on the configuration of the ForkParser, it might be useful for that
> and also for tika-batch to write out each embedded file once the parse for
> that embedded file has completed, rather than caching the entire output in
> memory.
> The downside to this is that the main document will now show up at the bottom
> of the list of metadata objects. We can re-arrange when we deserialize, but
> anyone not using our deserialization will see this change in order. Given
> that this is a breaking change, I'll make it optional.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
