...
The Aspire Elasticsearch Provider is the component that is responsible for talking to Elasticsearch on behalf of Aspire. All configuration for
the Elasticsearch Provider in Aspire is done in the settings.xml file.
...
Elasticsearch provider can be configured to use Basic authentication if required by the Elasticsearch server administrator. Username and password must be provided. Password must be encrypted by standard Aspire encryption utilities.
Note | ||
---|---|---|
| ||
The Elasticsearch authentication was tested using the File Based authentication provided in the free tier. None of the security features included in the subscription tiers were tested nor they are officially supported. The security features were made available for free since version 6.8.0 and 7.1.0. For more information, please visit Elastic's official notice. |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- noSql database provider for the 4.0 connector framework --> <noSQLConnectionProvider> <implementation>com.accenture.aspire:aspire-elasticsearch-provider</implementation> <url>http://localhost:9200</url> <claimPrefetch>300</claimPrefetch> <claim>100</claim> </noSQLConnectionProvider> |
Elasticsearch provider can claim items from queues by in larger units and after changing queue items status from Available to InProgress they are sent back to Elasticsearch as a bulk unit. By With this technique we can achieve better performance. We can configure claim unit size parameters based on the current Aspire installation (e.g. standalone/ distributed mode, etc.). This is how it works:
...
Elasticsearch provider iterators use Elasticsearch scroll technique. The scrolls are resources which should be deleted after their use. This is done explicitly whenever possible by calling iterators close method or when the iteration is over. There are cases though when the iteration cannot be completed and in that case "unused scrolls " stay persist and can might potentially reach the limit of available resources. The parameter "keepSearchContextAlive" controls how long the scrolls should stay before deletion. The default value is "5m". The format of this parameter and other information is described here.
...
The Provider will bulk for better performance chosen operations if "useBulk" is true (default false). The above example values of remaining parameters are also their default values
...