Most operations in elasticsearch are through corresponding actions, which are in the action package. Its structure is shown in the figure below:
Shown here is a partial screenshot of the Action package, which contains Actions corresponding to various functions. The packages of each action are also very similar to index. These actions all inherit from the base action, so their implementation is very similar. The following figure shows the inheritance relationship of indexaction
These actions are just substitutes and do not implement real functions, so they are also very easy to implement. Their main function is to provide methods for creating new responses and requests, corresponding to the corresponding operation names. Take indexaction as an example. Its method diagram is as follows:
#You can see that it only provides two methods for creating response and request, and a NAME field. , this NAME field will be used in subsequent action calls. The corresponding function is implemented in the corresponding transportAction.
TransportAction interface is inherited by all tansportAction. When the client calls the relevant interface of the client, the client will send the request to the execute of transportAction. The TransportAction of each function implements the doExecute method, and the logic of the function is implemented in this method. We will not mention it here for now. The corresponding implementation will be seen in the subsequent functional analysis.
There is such a piece of code in the client analysis:
TransportAction
registerAction(NodesInfoAction.INSTANCE, TransportNodesInfoAction.class); registerAction(NodesStatsAction.INSTANCE, TransportNodesStatsAction.class); registerAction(NodesShutdownAction.INSTANCE, TransportNodesShutdownAction.class); registerAction(NodesRestartAction.INSTANCE, TransportNodesRestartAction.class); registerAction(NodesHotThreadsAction.INSTANCE, TransportNodesHotThreadsAction.class); registerAction(ClusterStatsAction.INSTANCE, TransportClusterStatsAction.class); registerAction(ClusterStateAction.INSTANCE, TransportClusterStateAction.class); registerAction(ClusterHealthAction.INSTANCE, TransportClusterHealthAction.class)
Only part of the content is shown here, where the module will bind the corresponding action and TransportAction. In this way, when the client needs to receive a request, it will find the corresponding tansportAction instance according to the corresponding action instance, and the final request will be processed under them.
The above is the detailed content of How to implement elasticsearch java client action. For more information, please follow other related articles on the PHP Chinese website!

Start Spring using IntelliJIDEAUltimate version...

When using MyBatis-Plus or other ORM frameworks for database operations, it is often necessary to construct query conditions based on the attribute name of the entity class. If you manually every time...

Java...

How does the Redis caching solution realize the requirements of product ranking list? During the development process, we often need to deal with the requirements of rankings, such as displaying a...

Conversion of Java Objects and Arrays: In-depth discussion of the risks and correct methods of cast type conversion Many Java beginners will encounter the conversion of an object into an array...

Solutions to convert names to numbers to implement sorting In many application scenarios, users may need to sort in groups, especially in one...

Detailed explanation of the design of SKU and SPU tables on e-commerce platforms This article will discuss the database design issues of SKU and SPU in e-commerce platforms, especially how to deal with user-defined sales...

How to set the SpringBoot project default run configuration list in Idea using IntelliJ...


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

Dreamweaver Mac version
Visual web development tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software