Get Alias APIedit

Get Alias Requestedit

The Get Alias API uses GetAliasesRequest as its request object. One or more aliases can be optionally provided either at construction time or later on through the relevant setter method.

GetAliasesRequest request = new GetAliasesRequest();
GetAliasesRequest requestWithAlias = new GetAliasesRequest("alias1");
GetAliasesRequest requestWithAliases =
        new GetAliasesRequest(new String[]{"alias1", "alias2"});

Optional argumentsedit

The following arguments can optionally be provided:


One or more aliases to retrieve


The index or indices that the alias is associated with


Setting IndicesOptions controls how unavailable indices are resolved and how wildcard expressions are expanded when looking for aliases that belong to specified indices.


The local flag (defaults to false) controls whether the aliases need to be looked up in the local cluster state or in the cluster state held by the elected master node

Synchronous executionedit

When executing a GetAliasesRequest in the following manner, the client waits for the GetAliasesResponse to be returned before continuing with code execution:

GetAliasesResponse response = client.indices().getAlias(request, requestOptions);

Synchronous calls may throw an IOException in case of either failing to parse the REST response in the high-level REST client, the request times out or similar cases where there is no response coming back from the server.

In cases where the server returns a 4xx or 5xx error code, the high-level client tries to parse the response body error details instead and then throws a generic ElasticsearchException and adds the original ResponseException as a suppressed exception to it.

Asynchronous executionedit

Executing a GetAliasesRequest can also be done in an asynchronous fashion so that the client can return directly. Users need to specify how the response or potential failures will be handled by passing the request and a listener to the asynchronous get-alias method:

client.indices().getAliasAsync(request, requestOptions, listener); 

The GetAliasesRequest to execute and the ActionListener to use when the execution completes

The asynchronous method does not block and returns immediately. Once it is completed the ActionListener is called back using the onResponse method if the execution successfully completed or using the onFailure method if it failed. Failure scenarios and expected exceptions are the same as in the synchronous execution case.

A typical listener for get-alias looks like:

ActionListener<GetAliasesResponse> listener =
        new ActionListener<GetAliasesResponse>() {
            public void onResponse(GetAliasesResponse getAliasesResponse) {

            public void onFailure(Exception e) {

Called when the execution is successfully completed.

Called when the whole GetAliasesRequest fails.

Get Alias Responseedit

The returned GetAliasesResponse allows to retrieve information about the executed operation as follows:

Map<String, Set<AliasMetadata>> aliases = response.getAliases(); 

Retrieves a map of indices and their aliases

GetAliasesResponse class contains information about errors if they occurred. This info could be in fields error or exception depends on a case.

RestStatus status = response.status(); 
ElasticsearchException exception = response.getException(); 
String error = response.getError(); 

Client sets status to NOT_FOUND if at least one item of specified indices or aliases is not found. Otherwise it is OK.

If at least one item of specified indices isn’t exist client sets ElasticsearchException and returns empty result.

If at least one item of specified aliases ins’t exist client puts error description in error field and returns partial result if any of other patterns match.

If user specified indices or aliases as regular expressions and nothing was found client returns OK status and no errors.