aglinxinyuan opened a new pull request, #6823:
URL: https://github.com/apache/texera/pull/6823

   ### What changes were proposed in this PR?
   
   Adds unit coverage for three workflow-core storage classes (all verified 
with the JBR-17 sbt toolchain; no source changes).
   - `DocumentFactorySpec` (extended): the full scheme-dispatch surface of 
`openReadonlyDocument`/`openDocument`/`createDocument`/`documentExists` — 
dataset/file/vfs arms, the unsupported-scheme guards (each asserting the 
operation-specific message), and the vfs create/open/exists happy paths across 
the RESULT/STATE/CONSOLE_MESSAGES/RUNTIME_STATISTICS namespaces, against a real 
local Iceberg catalog.
   - `DatasetFileDocumentSpec` (extended): the companion-object env-fallback 
lazy vals (presign-URL endpoint default, empty JWT default). The 
LakeFS/network-backed read paths are left uncovered as they need a live LakeFS.
   - `IcebergDocumentSpec` (new, unit-level — not `@IntegrationTest`): 
`getURI`, `getCount`, `get`/`getRange`/`getAfter` (with column projection + 
multi-file ordering + iterator exhaustion), `getTableStatistics`, 
`getTotalFileSize`, `asInputStream` (ZIP with parquet entries), and `clear` — 
driven against a real local Hadoop Iceberg catalog via a new 
`LocalHadoopIcebergCatalog` test helper.
   
   ### Any related issues, documentation, discussions?
   
   Closes #6821.
   
   ### How was this PR tested?
   
   `sbt -java-home <jbr-17> "WorkflowCore/testOnly *DocumentFactorySpec 
*DatasetFileDocumentSpec *IcebergDocumentSpec"` -> 49 succeeded, 0 failed. 
scalafmtCheckAll + scalafixAll --check clean.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.8 [1M context])


-- 
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