e305a6bed7
* Name `BulkItemResponse` ctors `BulkItemResponse` can contain either a success or failure. This replaces the two constructors used to build either case with named static methods. So instead of ``` return new BulkItemResponse(0, OpType.CREATE, createResponse); return new BulkItemResponse(0, OpType.CREATE, failure); ``` you now use ``` return BulkItemResponse.success(0, OpType.CREATE, createResponse); return BulkItemResponse.failure(0, OpType.CREATE, failure); ``` This makes it marginally easier to read code building these things - you don't have to know the type of the parameter to know if its a failure or success. * Consistent * Mock response |
||
|---|---|---|
| .. | ||
| src/main/java/org/elasticsearch/plugin/noop | ||
| README.md | ||
| build.gradle | ||
README.md
Purpose
This plugin provides empty REST and transport endpoints for bulk indexing and search. It is used to avoid accidental server-side bottlenecks in client-side benchmarking.
Build Instructions
Build the plugin with gradle :client:client-benchmark-noop-api-plugin:assemble from the Elasticsearch root project directory.
Installation Instructions
After, the binary has been built, install it with bin/elasticsearch-plugin install file:///full/path/to/noop-plugin.zip.
Usage
The plugin provides two REST endpoints:
/_noop_bulkand all variations that the bulk endpoint provides (except that all no op endpoints are called_noop_bulkinstead of_bulk)_noop_searchand all variations that the search endpoint provides (except that all no op endpoints are called_noop_searchinstead of_search)
The corresponding transport actions are:
org.elasticsearch.plugin.noop.action.bulk.TransportNoopBulkActionorg.elasticsearch.plugin.noop.action.search.TransportNoopSearchAction