[gdal-dev] FileGDB locks don't produce error during indexing

Travis Featherston bespin at gmail.com
Tue Jun 20 19:35:47 PDT 2017

I have 2 concurrent processes creating indexes on FileGDB tables.  I
expected to receive some sort of error or warning due to locking.
Unfortunately, both processes complete without any message or error. The
end result is that one of the indexes gets created and the other does not.

Run in 2 shells concurrently
ogrinfo -sql "create index ndx_one on foo_table (field1)" C:\temp\my.gdb
ogrinfo -sql "create index ndx_two on foo_table (field2)" C:\temp\my.gdb

Both return the following message but only one index is actually created.
INFO: Open of `C:\temp\my.gdb'
      using driver `FileGDB' successful.

I actually found this during some processing using python/ogr like this.
Nothing gets raised here either.
driver = ogr.GetDriverByName('FileGDB')
ds = driver.Open(self.gdb, 0)
layer = ds.GetLayer(self.fc)
sqlcmd = "create index {0} on {1}({2})".format(self.ndx_name, self.fc,
ds = None

Is there anything I can do to catch this at runtime?  At the very least is
there a pattern to look for the existence of an index?  I went through
different dialects and couldn't figure anything out.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20170620/6b1ada0d/attachment.html>

More information about the gdal-dev mailing list