Create a new data collection or update an existing one.
An optional tag to match against the specified blob.
The name of a collection.
JSON-formatted configuration values.
Solr hard commit inherited from the collection's solrconfig.xml that is designated as Fusion's default parameter for Solr data commits. Number of seconds in which the data is saved, but this parameter does not force the search results to refresh immediately. With this setting, search performance is not slowed, but the new data may not show in search results until the next refresh. Default value is 15.
Solr soft commit that does not save the data, but makes the data visible to searches almost immediately. If the system crashes, that new data is lost because it has not been saved. Default is false, and search visibility is managed using the commitWithin setting.
Solr's commitWithin parameter, configured at the collection level with a default of 10000 milliseconds, ensures data is committed and available for searching within 10 seconds. The default for signals collections is 1000 milliseconds. Fusion uses commitWithin to avoid relying on specific Solr-side configurations. The com.lucidworks.apollo.solr.commitWithin global property defines the default commitWithin for all documents added through Fusion. When you create a new collection in Fusion, its per-collection commitWithin is initialized from this global default.
DATA, LOGS, METRICS, SIGNALS, SIGNALS_AGGREGATION, SEARCHLOGS, SYNONYMS, RECOMMENDATIONS, HISTORY, BLOBS, MESSAGES, TAXONOMY, CRAWL_DB, JOB_HISTORY, ARCHIVING, AUTOCOMPLETE_DOCUMENTS, QUERY_REWRITE, USER_PREFS, JOB_REPORTS, ACL, NULL successful operation
Solr hard commit inherited from the collection's solrconfig.xml that is designated as Fusion's default parameter for Solr data commits. Number of seconds in which the data is saved, but this parameter does not force the search results to refresh immediately. With this setting, search performance is not slowed, but the new data may not show in search results until the next refresh. Default value is 15.
Solr soft commit that does not save the data, but makes the data visible to searches almost immediately. If the system crashes, that new data is lost because it has not been saved. Default is false, and search visibility is managed using the commitWithin setting.
Solr's commitWithin parameter, configured at the collection level with a default of 10000 milliseconds, ensures data is committed and available for searching within 10 seconds. The default for signals collections is 1000 milliseconds. Fusion uses commitWithin to avoid relying on specific Solr-side configurations. The com.lucidworks.apollo.solr.commitWithin global property defines the default commitWithin for all documents added through Fusion. When you create a new collection in Fusion, its per-collection commitWithin is initialized from this global default.
DATA, LOGS, METRICS, SIGNALS, SIGNALS_AGGREGATION, SEARCHLOGS, SYNONYMS, RECOMMENDATIONS, HISTORY, BLOBS, MESSAGES, TAXONOMY, CRAWL_DB, JOB_HISTORY, ARCHIVING, AUTOCOMPLETE_DOCUMENTS, QUERY_REWRITE, USER_PREFS, JOB_REPORTS, ACL, NULL