| Re: [geomesa-users] "explain" command line tool |
|
Hello, The filesystem data store is more rudimentary than most of our data stores, and it doesn't support explain planning yet. In general, the planning is not very interesting, as typically the partitions are broad (e.g. when using something like 'daily,z2:2-bits', there are 4 spatial quadrants per day). If you are using multi-threading (the default, controllable via data store parameter "fs.read-threads"), then you can see which partitions are being hit for a given query by enabling debug logging on 'org.locationtech.geomesa.fs'. Which data store implementation to pick depends on your use case. The filesystem data store is very easy to get started with, and provides extremely low operating costs if you run it on something like s3. Using a full-fledged database like HBase or Accumulo can up your setup complexity and operating costs considerably, but gives you much more fine-grained query capabilities, as well as distributed push-down processing. If you generally code to the geotools data store API (and/or the spark API), then it should be fairly trivial (from a client perspective) to switch between data store implementations. Roughly, they all offer the same capabilities, but some operations may be (much) slower depending on the implementation, and a few things may not be implemented everywhere (i.e. the explain command). Since you are in the exploratory phase, the filesystem datastore should give you a decent idea of the *kind* of things that you can do, with the understanding that it may not be the *fastest* you could do them. Thanks, Emilio On 12/16/18 1:49 PM, Andrew Ames wrote:
|