The GitHub Actions job "Java CI with Maven" on stormcrawler.git/fix-2097-tika-parse-timeout has failed. Run started by GitHub user rzo1 (triggered by rzo1).
Head commit for run: b75e1bad1f311b7a357ccb0f46bdafcee55e5d38 / Richard Zowalla <[email protected]> #2097 Tika ParserBolt: optional timeout for the parse with parser.tika.timeout The parse ran on the executor thread with no time limit, so a document which kept a parser busy held that thread for as long as it took, and the tuple timed out and was replayed into the same parse. The new key parser.tika.timeout sets the maximum time in milliseconds a document may take to parse. When it is set, the parse runs on a separate thread and the bolt waits for it up to that time. A document which takes longer is sent to the status stream as an ERROR with the message "parse timeout" and counted under error_parse_timeout. The parsing thread is interrupted, and the content handler stops the parse at its next SAX event; a parser which neither produces output nor checks for interrupts keeps its thread until it returns, so the bolt moves on to a new thread for the following documents. Parse errors and the text limit behave as before. The default stays -1 so the behaviour does not change unless the key is set. Report URL: https://github.com/apache/stormcrawler/actions/runs/35896645740 With regards, GitHub Actions via GitBox
