Hi Emily,
We have a mechanism to
export vector data in bulk to a single or set of compressed Avro files that also match a
supported ingest format for easy bulk ingest. This can be used to transfer data from disconnected GeoWave instances, backup data, or re-index using a different indexing scheme (or perhaps any other data migration oriented task). This can be used to transfer data from disconnected GeoWave instances, backup data, or re-index using a different indexing scheme (or perhaps any other data migration oriented task)The export commands are `geowave vector localexport` which writes to a single file and `geowave vector mrexport` which writes to a directory, a file per input split. For "mrexport," if you have hadoop installed locally you also may find it easier to run `hadoop jar /usr/local/geowave/tools/
geowave-<version/vendor>-tools.jar` instead of the geowave command. Otherwise it will remotely submit the job using the yarn resource manager, but `hadoop jar ...` ensures hadoop environment variables are setup which minimizes config issues depending on the environment.
However, it seems like you are more interested in downloading subsets in common OGC formats to perhaps use in another tool. I think if this is the need, the most general purpose mechanism is to use GeoServer through WMS and WFS. Within the "Layer Preview" tab, if you select the drop-down under "All Formats" you can see the set of supported formats. Although it is not a completely distributed process like the "mrexport" command, it is very general-purpose with many possible formats and at least the query/scan part runs distributed.
Let us know if you have other questions.
Rich
PS yes its the right forum, a lot of the core team was just out of town last week
