22.4. Trino Connector Configuration¶
The spatial_iceberg connector is configured through catalog properties in its .properties file (see Installing GeoMesa Trino).
Any property that does not start with geomesa.* is passed through unchanged to the stock
Iceberg connector. The following GeoMesa-specific properties are
supported:
Catalog property |
Default |
Description |
|---|---|---|
|
|
Enables connector-side, pre-decode bbox filtering in the page source (see below). |
|
— |
Trino-layer row-visibility enforcement; see Trino Data Store Security. |
22.4.1. Bounding-box page filtering¶
geomesa.spatial.bbox-page-filter controls whether the connector injects a bounding-box filter for spatial predicates. The
filter can eliminate rows based on fast bounding box comparisons, without having to decode the full binary geometry
value. But when disabled, the bounding box columns can be skipped, resulting in higher throughput. Thus, the filter is most
useful when it eliminates many rows, for example when data is coarsely partitioned. Otherwise, regular manifest and
file-level pruning may be sufficient. See Trino Data Store Design for more details on query pruning.