| [geomesa-users] indexes on non-point geometries |
|
We are in the process of upgrading to Geomesa 1.2.6 because we have point geometries and secondary non-point geometries on our data (currently polygons but expect to have line strings as well as additional data to the point).
In looking at the Data Management section for 1.2.6, I felt it implied by default it will see it is a non-point geometry and then will create the XZ2 and XZ3 (if there is time) indexes on createSchema.
So my questions are: -
If a polygon geometry exists but is not the default geometry for the schema (a point currently is the default geometry), will it recognize there is second geometry, a polygon, for example, and then create XZ2 and XZ3 indexes on it? -
If it will support indexing additional geometries beyond the default geom (the point) for one schema, is there a job one could run if the schema/catalog was created pre 1.2.5+ geomesa?
We want to get better performance for our ellipse/polygon rendering. As you can tell our current approach was to have one schema that has both the point and polygon. Curious if the indexing enhancements of 1.2.5+ will help if it is in
the same schema or if we need to split ellipses/polygons into their own schema where they are the default geometry to get better indexing on them. I was unclear if having all geometries in one schema would hurt/negate our ability to leverage the new indexes
or if there was a way to tell it to create those indexes as well. Thanks, Diane |