goutamadwant opened a new pull request, #11813:
URL: https://github.com/apache/seatunnel/pull/11813
### Purpose of this pull request
Related to #11801.
This is a design and compatibility PoC, not the production anydoc
integration.
It verifies that Markdown produced from an existing Excel fixture by the
anydoc CLI can enter the current `MarkdownReadStrategy` path while keeping RAG
document and chunk metadata tied to the original source URI.
The draft:
- extracts a package-private Markdown handoff method while keeping the
existing Markdown read path unchanged
- adds a deterministic anydoc-generated fixture and focused RAG metadata
coverage
- documents the external executable, WebAssembly, and sidecar choices in
English and Chinese
- records the packaging, platform, resource-limit, error, table-parsing,
licensing, and maintenance decisions required before production implementation
It does not add an anydoc dependency, executable, file format, configuration
option, or public API.
### Does this PR introduce _any_ user-facing change?
No. Existing PDF and Markdown behavior remains unchanged. This draft does
not expose an anydoc backend to users.
### How was this patch tested?
Generated the Markdown fixture from the existing Excel fixture using the
anydoc CLI.
Verified with:
```shell
./mvnw -pl seatunnel-connectors-v2/connector-file/connector-file-base \
-Dtest=MarkdownReadStrategyTest test
./mvnw -pl seatunnel-connectors-v2/connector-file/connector-file-base \
-DskipITs package
```
The focused test class completed with 6 tests passing. The module package
completed with 248 tests passing.
### Check list
* [x] No new Jar binary package or runtime dependency is added.
* [x] English and Chinese design notes are included.
* [x] No incompatible change is introduced.
* [x] Connector packaging and plugin configuration remain unchanged because
this draft does not add a production parser backend.
--
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]
