lance_table::format

Module pb

Source
Expand description

Protobuf definitions for Lance Format

Modules§

Structs§

  • Currently these are all empty messages because all needed details are either hard-coded (e.g. filenames) or stored in the index itself. However, we may want to add more details in the future, in particular we can add details that may be useful for planning queries (e.g. don’t force us to load the index until we know we need it)
  • Lance Data File
  • Data fragment. A fragment is a set of files which represent the different columns of the same rows. If column exists in the schema, but the related file does not exist, treat this column as nulls.
  • Deletion File
  • / A basic bitpacked array of u64 values.
  • Metadata describing the index.
  • Index Section, containing a list of index metadata for one dataset version.
  • Manifest is a global section shared between all the files.
  • / 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.
  • A transaction represents the changes to a dataset.
  • / Different ways to encode a sequence of u64 values.
  • / UUID type. encoded as 16 bytes.
  • Auxiliary Data attached to a version. Only load on-demand.