[geomesa-users] What are best practices for rollback and possible update

[Benjamin Weaver <Benjamin.Weaver@xxxxxxxxxxxxxxxxxx>]

Hi all,

We are using Geomesa 1.2.1 on Accumulo 1.7.2. We are seeking to implement a rollback procedure to use during Ingest. This is our first priority; a second would be the ability to update data already in the database. We lack the space to maintain a backup copy of our large tables. We have one large Accumulo table containing 1 geomesa SimpleFeature.

Load of a staging table, followed by geomesa cmd-line export of this table, and merge of this export into our main table, shows some promise as a hedge during ingest. Another approach would seem represented by the Accumulo command line, which enables row deletions but I did not know whether Accumulo shell could gracefully handle the Geomesa table suite.

But what is the best way to rollback on mid-way failure of ingest? Are examples available? I saw some Scala classes that include calls to trans.rollback(), etc. Are these or other classes to be used for batch, or bulk or total rollback? Or are there other rollback tools and techniques I have overlooked?

Any perspectives are appreciated and welcome!

Ben Weaver

This email (and any attachments) may contain confidential information and is intended solely for the recipient(s) to whom the email is addressed. If you received this email in error, please inform us immediately and delete the email and all attachments without further using, copying or disclosing the information. This email and any attachments are believed to be, but cannot be guaranteed to be, secure or virus-free. Satellite Applications Catapult Limited is registered in England & Wales. Company Number: 7964746. Registered office: Electron Building, Fermi Avenue, Harwell Oxford, Didcot, Oxfordshire OX11 0QR.