Expand description
Protobuf definitions for Lance Format
Modules§
- data_
fragment - Nested message and enum types in
DataFragment. - deletion_
file - Nested message and enum types in
DeletionFile. - encoded_
u64_ array - Nested message and enum types in
EncodedU64Array. - fragment_
reuse_ index_ details - Nested message and enum types in
FragmentReuseIndexDetails. - manifest
- Nested message and enum types in
Manifest. - mem_
wal_ index_ details - Nested message and enum types in
MemWalIndexDetails. - transaction
- Nested message and enum types in
Transaction. - u64_
segment - Nested message and enum types in
U64Segment.
Structs§
- Base
Path - external dataset base path
- Data
File - Data
Fragment - A DataFragment is a set of files which represent the different columns of the same rows. If column exists in the schema of a dataset, but the file for that column does not exist within a DataFragment of that dataset, that column consists entirely of nulls.
- Deletion
File - Deletion File
- Encoded
U64Array - / A basic bitpacked array of u64 values.
- External
File - Fragment
Reuse Index Details - Index
Metadata - Metadata describing an index.
- Index
Section - Index Section, containing a list of index metadata for one dataset version.
- Manifest
- Manifest is a global section shared between all the files.
- MemWal
Index Details - RowId
Sequence - / A sequence of row IDs. This is split up into one or more segments, / each of which can be encoded in different ways. The encodings are optimized / for values that are sorted, which will often be the case with row ids. / They also have optimized forms depending on how sparse the values are.
- Transaction
- A transaction represents the changes to a dataset.
- U64Segment
- / Different ways to encode a sequence of u64 values.
- Uuid
- UUID type. encoded as 16 bytes.
- Vector
Index Details - Empty details messages for older indexes that don’t take advantage of the details field.
- Version
AuxData - Auxiliary Data attached to a version. Only load on-demand.