feat(spec): formally split catalog, namespace, table and index specs#6566
Conversation
795ebbd to
1ea93e1
Compare
| - The **catalog specs** define how tables are discovered, registered, and coordinated across engines and services. | ||
|
|
||
| ### 2. File Format | ||
| The architecture is designed around Apache Arrow boundaries. Once data is in memory, Arrow is the interchange format. Only table readers, table writers, and index readers or writers need to know the on-disk Lance file layout. |
There was a problem hiding this comment.
nitpick: Honestly, I think that the Arrow in-memory format is a library implementation detail. If another library was implemented to read and write Lance tables, it could choose whatever in-memory representation it want.
There was a problem hiding this comment.
updated, let me know what you think about the new wording.
## Summary - split the catalog and namespace specification docs for downstream assembly - fix supported catalog links for the new layout - restore the overview and Java SDK diagrams on the namespace spec page Lance PR: lance-format/lance#6566 Preview: https://jackye1995.github.io/lance/
|
ACTION NEEDED The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification. For details on the error please inspect the "PR Title Check" action. |
I will do that as a separate fix. I already squeezed quite some style and ci changes to this PR, should probably not touch anything else at this point |


Summary
Namespace PR: lance-format/lance-namespace#326
Vote: #6567
Preview: https://jackye1995.github.io/lance/