Add options that can be provided to AccumuloDataStore and GeoWaveDataStore to change some behaviors but have reasonable defaults be the current behavior if no options are specified. A few examples to start out would be to enable/disable persisting a data adapter in the metadata table if it doesn't exist, enable/disable persisting an index in the metadata table if it doesn't exist, and enable/disable creating an index table if it doesn't exist (probably just throwing an error if it doesn't exist).
Another option in which the default behavior is currently not implemented is to enable/disable automatically adding a locality group for a new column family (data adapter ID) within an index table. It seems the default behavior would be to create a locality group for each column family because this is the most typical access pattern.
Add options that can be provided to AccumuloDataStore and GeoWaveDataStore to change some behaviors but have reasonable defaults be the current behavior if no options are specified. A few examples to start out would be to enable/disable persisting a data adapter in the metadata table if it doesn't exist, enable/disable persisting an index in the metadata table if it doesn't exist, and enable/disable creating an index table if it doesn't exist (probably just throwing an error if it doesn't exist).
Another option in which the default behavior is currently not implemented is to enable/disable automatically adding a locality group for a new column family (data adapter ID) within an index table. It seems the default behavior would be to create a locality group for each column family because this is the most typical access pattern.