keksmd opened a new issue, #945:
URL: https://github.com/apache/incubator-graphar/issues/945

   ## Problem
   
   The published development container cannot build the current C++ library 
against the Arrow and Parquet packages installed by its own Dockerfile. This 
blocks the cross-language GraphInfo compatibility gate for the pure-Java SDK 
and affects the C++ build independently of Java changes.
   
   ## Reproduction
   
   Run in `ghcr.io/apache/graphar-dev:latest`:
   
   ```text
   cmake -S cpp -B /tmp/graphar-build -DBUILD_TESTS=OFF 
-DCMAKE_BUILD_TYPE=Release
   cmake --build /tmp/graphar-build -j2
   ```
   
   The build fails in untouched C++ sources. Representative errors:
   
   ```text
   arrow::compute::Initialize is not a member of arrow::compute
   parquet::arrow::FileReader::ReadTable requires output-pointer arguments
   arrow::adapters::orc types are not available
   ```
   
   The same incompatibility appears when compiling only the GraphInfo loader 
path, because `filesystem.cc` includes the affected Arrow/Parquet API surface.
   
   ## Scope
   
   - Make the pinned devcontainer Arrow/Parquet version compatible with the C++ 
source, or update the C++ compatibility layer to the installed API.
   - Restore a successful CMake library build in the published devcontainer.
   - Add a CI/devcontainer verification that catches this dependency drift.
   
   ## Non-goals
   
   - No Java SDK feature changes.
   - No GraphAr format semantic changes.
   
   ## Links
   
   - The blocked Java metadata cross-language acceptance gate: #944
   - Java architecture discussion: #756
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to