You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Initial 1.0.0 commit
* fixed conformance
* Added CORS config
* tiny typo (#17)
Saw a tiny typo and wanted to get on the board. Great stuff
* Removed properties from collections
Co-authored-by: zachrouseFE <39569018+zachrouseFE@users.noreply.github.com>
-[https://stac.boundlessgeo.io/search?query=landsat:wrs_path=105 AND landsat:wrs_row=83](https://stac.boundlessgeo.io/stac/search?query=landsat:wrs_path=105%20AND%20landsat:wrs_row=83)
The STAC API has several properties that are configurable from the command line, as environment properties in the
@@ -178,7 +87,7 @@ staccato.es.host | localhost | The hostname of the Elasticsearch aggregationServ
178
87
staccato.es.port | 9200 | The Elasticsearch aggregationService port
179
88
staccato.es.number-of-shards | 5 | The number of shards used when auto-initializing an Elasticsearch index
180
89
staccato.es.number-of-replicas | 0 | The number of replicas used when auto-initializing an Elasticsearch index
181
-
staccato.es.type | _doc | The Elasticsearch document type. It is not recommended to change this from it's default value as "_doc" will be the only value supported in ES7
90
+
staccato.es.type | _doc | The Elasticsearch document type. It is not recommended to change this from its default value as "_doc" will be the only value supported in ES7
182
91
staccato.es.max-reconnection-attempts | 10 | The number of reconnection attempts to the Elasticsearch aggregationService
183
92
staccato.es.rest-client-max-connections-total | 200 | The Elasticsearch client threadpool size. This is the maximum number of connections a single STAC instance may have open to Elasticsearch.
184
93
staccato.es.rest-client-max-connections-per-route | 200 | The maximum number of Elasticsearch client connections per route.
@@ -310,7 +219,7 @@ It is also important to note that this implementation currently relies on implem
310
219
the `collection` field in every item. Because each collection will have a different properties implementation that may
311
220
implement several different extension interfaces or custom fieldsExtension, Jackson cannot deserialize Item classes without
312
221
more information on which properties class to deserialize to. Having the "collections" field in each item provides an
313
-
extremely convenient 1:1 relationship between the item and it's properties implementation. The Jackson configuration
222
+
extremely convenient 1:1 relationship between the item and its properties implementation. The Jackson configuration
314
223
for this can be found [here](./staccato-application/src/main/java/com/planet/staccato/config/ExtensionConfig.java).
315
224
316
225
### Custom annotations
@@ -331,7 +240,6 @@ methods with this annotation and build a subcatalog link containing the field na
331
240
containing all unique values in Elasticsearch for that field. After all eligible subcatalog fieldsExtension have been
332
241
traversed, the links section will be populated with links to all items that match the selected subcatalog values.
333
242
334
-
335
243
## Elasticsearch
336
244
337
245
### Automatic Initialization
@@ -414,7 +322,7 @@ Elasticsearch to rollover the index. When the criteria has been met, Elasticsea
414
322
index named `my-index-name-000002`. Because this name matches the pattern `my-index-name-*` that was established in
415
323
our template, all of the shard, read replica, mapping, etc configuration will automatically be applied. In addition,
416
324
the `my-index-name` write alias will automatically be changed to point to `my-index-name-000002`, and the search alias
417
-
`my-index-name-search` will add to it's list. `my-index-name-000002`. When executing searches against the search
325
+
`my-index-name-search` will add to its list. `my-index-name-000002`. When executing searches against the search
418
326
alias `my=index-name-search`, Elasticsearch will return matches from both indexes, `my-index-name-000001` and
419
327
`my-index-name-000002`. The one important note: if a record needs to be updated, you need to first determine which
420
328
actual index it belongs to and update it on that index.
0 commit comments