We have a field that holds config keys here:
|
// Table config. |
|
// |
|
// Keys with the prefix "lance." are reserved for the Lance library. Other |
|
// libraries may wish to similarly prefix their configuration keys |
|
// appropriately. |
|
map<string, string> config = 16; |
We say that there are some prefixed with lance.. We should expect any library that supports the Lance format can read these and understand them. To help that along, we should have a documentation page in under "Specification" that lists all the known ones and what they do. This can be a table. Each entry can link to another documentation page that describes the feature more fully.
Part of this task is going through the library and identifying all the lance. prefixes that are used.
We have a field that holds config keys here:
lance/protos/table.proto
Lines 184 to 189 in 779f6e6
We say that there are some prefixed with
lance.. We should expect any library that supports the Lance format can read these and understand them. To help that along, we should have a documentation page in under "Specification" that lists all the known ones and what they do. This can be a table. Each entry can link to another documentation page that describes the feature more fully.Part of this task is going through the library and identifying all the
lance.prefixes that are used.