Hi all,
A couple caveats:
In GeoMesa, the row key contains the temporal and spatial data for
the feature. So if you try to overwrite a feature by keeping the
same feature ID, but you change the location and/or time, it will
create a new row and not overwrite the existing entry.
If you do overwrite the exact same row, Accumulo by default will
apply a VersioningIterator so that you only see the latest entry.
You can change this behavior if you want:
http://accumulo.apache.org/1.5/accumulo_user_manual.html#_versioning_iterators_and_timestamps
I would encourage people to check out the GeoMesa quick start
tutorial:
http://geomesa.github.io/2014/05/28/geomesa-quickstart/
It lets you write and read just a few features at a time through the
API. You can test out your exact scenario and determine what works
for you.
Thanks,
- Emilio
On 06/20/2014 08:13 AM, Anthony Fox
wrote:
Beau, Jim,
If you overwrite records with the same id, then you'll observe
multiple records until Accumulo performs a table compaction or
you set a versioning iterator. Since this sounds like a valid
use case, we can by default set a versioning iterator so you
only see the most recent version of your record. Table
compactions will periodically remove stale data.
-Anthony
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
http://www.locationtech.org/mailman/listinfo/geomesa-users
|