[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [geomesa-users] Possible bug with removing features, cannot add a feature with same ID as a feature that has been removed
|
Anthony,
Thanks for the reply.
In my test and also in our real system we have witnessed this problem writing to accumulo from a single client (not using a map-reduce job). I should mention that accumulo is not on the same machine as the client that we are using to write.
In our real system I am confident that there is elapsed system time between the remove and add calls - in our junit test (partial code in original post), there might not be much elapsed time because of the simplicity of the test.
Thanks for your help,
Beau
Sent from my mobile device.
On Jul 21, 2014 8:13 AM, Anthony Fox <anthonyfox@xxxxxxxx> wrote:
Beau,
Yes, you definitely can add/remove/add without problems in Accumulo. The only time you cannot do it without strange behaviour is if you set the timestamp exactly the same for each 'add'. GeoMesa does not explicitly set the timestamp, so it should get the
current system time for each mutation. Can you tell me a bit more about how you are writing to GeoMesa? Is it from the same client (with consistent system time) each time or is it from within a map-reduce job? If the latter, do you have ntpd setup to synchronize
system time? I'll put together a test to see if we can reproduce your issue.
Thanks,
Anthony