SPARKNLP-1322 Store Structural Position for Tables and Images #14713
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
New Feature: Add structural metadata (domPath, orderTableIndex, orderImageIndex) across document readers
Bug Fix: Resolves a bug where certain elements (e.g., section titles and diagnosis entries) appeared multiple times in the parsed output on HTML files
Motivation and Context
Previously, our document parsers (HTMLReader, XMLReader, WordReader, PowerPointReader, ExcelReader) relied heavily on positional or page-based coordinates for layout metadata.
However, non-PDF formats such as HTML, XML, DOC(X), PPT(X), and XLS(X) do not have fixed pages
To ensure deterministic element referencing and structural traceability across all document types, we needed to adopt a unified DOM-like metadata model.
This change standardizes metadata extraction so every element can be uniquely identified and re-located within its source document, independent of visual layout.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: