[
https://issues.apache.org/jira/browse/TIKA-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322487#comment-17322487
]
Tim Allison commented on TIKA-3263:
-----------------------------------
[~kkrugler], I wasn't around when this was implemented, but my guess is that
throwing an exception halts the computational resources of parsing the
file...if you're not getting any more content, better to stop. That _may_ have
been the driver, but I've been bothered by this for a while.
[~aweber1nj], in our main branch (Tika 2.0), I've been working with a public
WriteLimitReachedException that extends SaxException for the
RecursiveParserWrapper. I have to get around to updating the
WriteoutContentHandler to use this.
> WriteLimitReachedException is not public
> ----------------------------------------
>
> Key: TIKA-3263
> URL: https://issues.apache.org/jira/browse/TIKA-3263
> Project: Tika
> Issue Type: Improvement
> Environment: Windows 10
> Reporter: Peter Kronenberg
> Priority: Minor
>
> I got a WriteLimitReachedException because my file was too big. The message
> tells me that the text up the limit is still available. However, it’s tricky
> to get that text and at the same time, respond appropriately to
> SAXExceptions. Originally, my method was catching SAXEXceptions and assume
> there was an error.
> What I really want to do it to be able to catch WriteLimitReachedException,
> but still throw other SAXExceptions, which would indicate that something else
> went wrong. But since WriteLimitReachedException is private, I can’t do that.
>
> Here’s what my code originally looked like:
> !Code1.png!
> But this didn’t work, because if I get a WriteLimitReachedException, it
> doesn’t tell me what data that it got
>
> Given this new knowledge, here’s what I want to do, but I can't, because
> WriteLimitReachedException is private. There's no reason for it to be
> private.
>
> !Code2.png!
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
