Andrew,
We are on
1.2.7.2 currently. So one could merge that iterator over
and then just apply the age off filter based on the DTG
field specified as the time field on ingest?
Any idea if
there are plans to add this type of iterator to the main
code base? I have to see if a custom code build is amenable
or not so that is one area of concern for me but we do have
to age off the data.
Thanks,
Diane
Diane,
I do have a GeomesaAgeOffIterator that I use in production
but it is not merged into the main codebase. The version I
have works on 1.2.x at the moment. You are on 1.2.7.3 right?
You can age things off with delete commands manually but this
is very tedious. I think the iterator is a better way. It
applies at scan, minc, and majc and can actually handle things
other than just dates. (e.g. data auths)
I'll send you something off list.
Andrew
On 04/28/2017 11:04 AM, Diane Griffith
wrote:
Is there a recommended strategy one can
use to age-off data leveraging accumulo age-off that will
clean up data after a certain date. I did not think just
applying an age-off filter manually would work.
We are currently on the 1.2.x code base
but I did see there was a GeomesaAgeoffIterator.scala so is
this something more readily supported in the 1.3.x code
base?
Is there a more manual recommended way to
do age-off (either define a date in the SFT that can be
used) across all tables created? If there is not one the
only thing we can figure which we want to avoid is querying
and doing manual deletes and assume that will clean up all
tables for a given sft (indexes and all).
Thanks,
Diane
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users