keksmd opened a new issue, #943:
URL: https://github.com/apache/incubator-graphar/issues/943
## Problem
The under-development pure-Java `graphar-info` module does not currently
expose the GraphAr v1 edge payload layout that the C++ implementation and
canonical fixtures use. Its prior API could not select the edge sub-chunk and
resolved count/offset files beneath an extra `adj_list/` segment.
This is the compatibility gate before any Java physical reader is
introduced. It is informed by the Java architecture discussion in #756.
## Scope
- Make edge URI resolution match the C++ `EdgeInfo` contract:
- `{edge}/{adj}/vertex_count`
- `{edge}/{adj}/edge_count{vertexChunk}`
- `{edge}/{adj}/adj_list/part{vertexChunk}/chunk{edgeChunk}`
- `{edge}/{adj}/offset/chunk{vertexChunk}`
- `{edge}/{adj}/{propertyGroup}/part{vertexChunk}/chunk{edgeChunk}`
- Require adjacency type, vertex chunk index, and edge chunk index for
topology and edge-property resolution.
- Normalize valid prefixes that omit a trailing slash.
- Test the generated paths against `testing/ldbc_sample/parquet`, including
a nonzero `part2/chunk1` edge chunk.
## Non-goals
- No physical Parquet/CSV/ORC reader or writer.
- No storage API, Arrow dependency, Hadoop dependency, or query AST.
## Acceptance criteria
1. Java and C++ return equal relative suffixes for vertex properties/counts
and all declared edge layout payloads.
2. Count and offset files are outside `adj_list/`; topology and edge
property chunks include both partition indices.
3. Tests cover an ordered source layout, ordered destination layout, paths
without trailing slashes, and a real fixture file.
4. `graphar-info` passes formatting and the full Maven verification suite in
the project devcontainer.
## Links
- Architecture discussion: #756
- Follow-up metadata parity: to be tracked separately.
--
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]
