21.2. Using the Kudu Data Store Programmatically¶
21.2.1. Creating a Data Store¶
An instance of a Kudu data store can be obtained through the normal GeoTools discovery methods, assuming that the GeoMesa code is on the classpath.
Map<String, Serializable> parameters = new HashMap<>();
parameters.put("kudu.master", "localhost");
parameters.put("kudu.catalog", "geomesa");
org.geotools.data.DataStore dataStore =
org.geotools.data.DataStoreFinder.getDataStore(parameters);
21.2.2. Kudu Data Store Parameters¶
The data store takes several parameters (required parameters are marked with *
):
Parameter |
Type |
Description |
---|---|---|
|
String |
The host name of the Kudu master server |
|
String |
The name of the GeoMesa catalog table |
|
String |
Kudu client authentication credentials |
|
String |
Number of worker threads used by the Kudu connection |
|
String |
Number of boss threads used by the Kudu connection |
|
Boolean |
Disable Kudu client statistics |
|
String |
Comma-delimited superset of authorizations that will be used for queries |
|
Boolean |
Audit queries being run. Queries will be written to a log file |
|
String |
The max time a query will be allowed to run before being killed. The
timeout is specified as a duration, e.g. |
|
Integer |
The number of threads to use per query |
|
Boolean |
Use loose bounding boxes - queries will be faster but may return extraneous results |
|
Boolean |
Toggle collection of statistics (currently not implemented) |
|
Boolean |
Toggle caching of results |
More information on using GeoTools can be found in the GeoTools user guide.