dependabot[bot] opened a new pull request, #2066:
URL: https://github.com/apache/stormcrawler/pull/2066

   Bumps `tika.version` from 3.3.2 to 4.0.0.
   Updates `org.apache.tika:tika-core` from 3.3.2 to 4.0.0
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/apache/tika/blob/main/CHANGES.txt";>org.apache.tika:tika-core's
 changelog</a>.</em></p>
   <blockquote>
   <p>Release 4.1.0 - unreleased</p>
   <ul>
   <li>
   <p>The Kafka pipes iterator no longer stops at the first empty poll. A newly
   subscribed consumer spends its first poll(s) joining the group and returns
   empty even when the topic has a backlog, so the iterator could enqueue zero
   files and report success. It now waits for a partition assignment (bounded
   by the new assignmentTimeoutMs, default 30s) and requires a continuous quiet
   window (drainIdleMs, default 1s) before concluding the topic is drained.
   groupInitialRebalanceDelayMs is deprecated and no longer sent to the
   consumer: it is a broker setting that Kafka has always ignored 
(TIKA-4833).</p>
   </li>
   <li>
   <p>Pipes IPC: carry inline document bytes as a raw binary field beside the
   tuple in the request envelope -- never inside the tuple or its
   ParseContext -- and disable Smile's 7-bit binary encoding. Tuple JSON
   serialized by 4.0.0 with an &quot;inline-bytes&quot; parse-context entry no 
longer
   loads; it is rejected with a tailored message (TIKA-4829).</p>
   </li>
   <li>
   <p>Digesting embedded documents no longer buffers each embedded object to a
   temp file. Zip entries are re-read from the parent archive on rewind, and
   a new process-wide CacheMemoryBudget (seeded by the pipes forked server;
   default 256MB, clamped to a quarter of the fork's heap; tunable via
   -Dtika.pipes.cacheMemoryBudgetBytes in the config's forkedJvmArgs, &lt;=0
   disables) lets embedded objects stay in memory past the per-object 1MB
   threshold. New public API on TikaInputStream: get(IOSupplier,...),
   enableRewind(CacheMemoryBudget), getSeekableByteChannel(). Zip/7z/epub/odf
   parsing and zip container detection now read through seekable channels, so
   after detection/parsing a TikaInputStream may no longer be file-backed
   (hasFile() false); getPath()/getFile() still work and spool on demand
   (TIKA-4828).</p>
   </li>
   <li>
   <p>Pipes now carries the caller-supplied Content-Type across the worker's
   fresh-metadata boundary as a soft detection hint, so every forked-parse
   endpoint (/tika, /meta, /rmeta, /unpack, /async, /pipes, plus tika-grpc
   and embedded PipesForkParser) can route on a client Content-Type, not
   only on the filename. Detection keeps the hint only when it equals or
   specializes the content-detected type (e.g. refining image/tiff to
   image/x-canon-cr2); for bytes with no magic it can select any type,
   matching the routing power the filename already had. The
   CONTENT_TYPE_USER_OVERRIDE key is deliberately not carried, so the hint
   cannot force an unrelated type (TIKA-4825).</p>
   </li>
   <li>
   <p>OneNote extraction now follows document order, omits superseded page
   revisions, sorts author metadata, extracts embedded object BLOBs, and
   bounds malformed-input recursion and file-derived allocations. Parse
   warnings and embedded relationship IDs are exposed in metadata. Malformed
   or truncated files that cannot be fully parsed, and files whose walk
   yields no content, now fall back to the legacy string dump instead of
   failing or returning empty output. The legacy MS-ONESTORE walker bounds
   its recursion (depth caps plus file-node-list and fragment-chain cycle
   guards) and now honors shouldParseEmbedded for embedded file data</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/apache/tika/commit/514e1b3d8d29726d02ac6a12479d95f5db263379";><code>514e1b3</code></a>
 [maven-release-plugin] prepare release 4.0.0-rc1</li>
   <li><a 
href="https://github.com/apache/tika/commit/4e39e0743878ad8e0d5a4019eabc08ff76911c3e";><code>4e39e07</code></a>
 revert second rc1 attempt</li>
   <li><a 
href="https://github.com/apache/tika/commit/7975986d2a4162e227bd120e386dc626602d09ce";><code>7975986</code></a>
 javadocs take 42</li>
   <li><a 
href="https://github.com/apache/tika/commit/95d423592d75d4f5d9fa0a4b25fe24d35ecb647d";><code>95d4235</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/apache/tika/commit/666289be6fd30ed3587329c8ca86ab883a5d36b2";><code>666289b</code></a>
 [maven-release-plugin] prepare release 4.0.0-rc1</li>
   <li><a 
href="https://github.com/apache/tika/commit/c9f6585992b4dc686457015c6d9650f7d55623af";><code>c9f6585</code></a>
 TIKA-4808 - revert aborted 4.0.0-rc1 release commits; fix per-module javadoc 
...</li>
   <li><a 
href="https://github.com/apache/tika/commit/41183e76e87862dc64468241abcd924569a11a1a";><code>41183e7</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/apache/tika/commit/5dd7fc74ee20630375f44daddd21efcd3a5df64b";><code>5dd7fc7</code></a>
 [maven-release-plugin] prepare release 4.0.0-rc1</li>
   <li><a 
href="https://github.com/apache/tika/commit/4b231cf01f622b62c4ff272787e993593b23a6aa";><code>4b231cf</code></a>
 TIKA-4808 -- prep CHANGES.txt for release</li>
   <li><a 
href="https://github.com/apache/tika/commit/532a685ea1bd4db96befd17447f3a9aec70bca54";><code>532a685</code></a>
 TIKA-4808 - remove access to the network parser from cli (<a 
href="https://redirect.github.com/apache/tika/issues/3036";>#3036</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/apache/tika/compare/3.3.2...4.0.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `org.apache.tika:tika-parsers-standard-package` from 3.3.2 to 4.0.0
   
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to