16.3. Index Configuration¶
When creating a new feature type using the GeoMesa FileSystem data store (FSDS), there are several required options
that must be specified. Through the command line tools, these options are exposed as flags. If using the GeoTools
data store API, the options must be set as user data before calling
16.3.1. Configuring the File Encoding¶
The FSDS currently supports three options for file encoding:
converter. Both ORC and
Parquet support reading and writing, while
converter is a synthetic, read-only format that supports querying
a wide variety of data files using the GeoMesa Convert API.
File encoding can be specified through the user data key
16.3.2. Configuring the Partition Scheme¶
Partition schemes define how data files are laid out in folders on the file system. Schemes are defined by a well-known name, and an optional map of configuration values. See Partition Schemes for more details.
Partition schemes can be specified through the user data key
16.3.3. Configuring Leaf Storage¶
Leaf storage controls the final layout of files and folders. When using leaf storage (which is enabled by default), the last component of the partition path is used as a prefix to the data file name, instead of as a separate folder. This can result in less directory overhead for filesystems such as S3.
As an example, a partition scheme of
yyyy/MM/dd would produce a partition path like
leaf storage, the data files for that partition would be
2016/01/01_<datafile>.parquet. If leaf storage is
disabled, the data files would be
2016/01/01/<datafile>.parquet, creating an extra level of directories.
Leaf storage can be specified through the user data key
16.3.4. Configuring Metadata Persistence¶
The FSDS keeps metadata on partitions and data files, to avoid repeatedly interrogating the file system. By default, metadata information is stored as a change log in the file system, which does not require any additional infrastructure. For more advanced use-cases, the FSDS also supports persisting metadata in a relational database using JDBC. For more information, see FileSystem Metadata.
Metadata persistence can be specified through the user data key