-
Notifications
You must be signed in to change notification settings - Fork 264
[DOCS] Adds the structure of the ES|QL docs #789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
1ba3eb3
[DOCS] Adds the structure of the ES|QL docs.
szabosteve 17401e5
[DOCS] Amends structure.
szabosteve c0d67a8
Apply suggestions from code review
szabosteve 65e26d3
Apply suggestions from code review
szabosteve 344b032
Merge branch 'main' into szabosteve/esql-docs-structure
szabosteve 1faa04e
[DOCS] Fine-tunes blueprint content.
szabosteve 42ea5ef
Merge branch 'szabosteve/esql-docs-structure' of github.com:elastic/e…
szabosteve b0a71a9
Merge branch 'main' into szabosteve/esql-docs-structure
szabosteve 2e24a68
Apply suggestions from code review
szabosteve 5c9b91d
Update docs/usage/esql.asciidoc
szabosteve 14046f7
added code examples
l-trotta 0a7737f
removed columnar adapter
l-trotta 5faa9f1
Merge branch 'main' into szabosteve/esql-docs-structure
szabosteve 5106377
[DOCS] Adjusts code block layout.
szabosteve File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,131 @@ | ||
[[esql]] | ||
=== ES|QL in the Java client | ||
|
||
This page helps you understand and use {ref}/esql.html[ES|QL] in the | ||
Java client. | ||
|
||
There are two ways to use ES|QL in the {java-client}: | ||
|
||
* Use the Elasticsearch {es-docs}/esql-apis.html[ES|QL API] directly: This | ||
is the most flexible approach, but it's also the most complex because you must handle | ||
results in their raw form. You can choose the precise format of results, | ||
such as JSON, CSV, or text. | ||
* Use ES|QL mapping helpers: These mappers take care of parsing the raw | ||
response into something readily usable by the application. Several mappers are | ||
available for different use cases, such as object mapping, cursor | ||
traversal of results, and dataframes. You can also define your own mapper for specific | ||
use cases. | ||
|
||
|
||
|
||
szabosteve marked this conversation as resolved.
Show resolved
Hide resolved
|
||
[discrete] | ||
[[esql-how-to]] | ||
==== How to use the ES|QL API | ||
|
||
The {es-docs}/esql-query-api.html[ES|QL query API] allows you to specify how | ||
results should be returned. You can choose a | ||
{es-docs}/esql-rest.html#esql-rest-format[response format] such as CSV, text, or | ||
JSON, then fine-tune it with parameters like column separators | ||
and locale. | ||
|
||
Because the response varies widely depending on the format, the | ||
{java-client} has a BinaryData object you can use according to the | ||
format specified in the request. | ||
|
||
The following example gets ES|QL results as CSV and parses them: | ||
|
||
[source,java] | ||
------------------------------------ | ||
String queryAuthor = | ||
""" | ||
from books | ||
| where author == "Isaac Asimov" | ||
| sort year desc | ||
| limit 10 | ||
"""; | ||
|
||
BinaryResponse response = client.esql().query(q -> q | ||
.format("csv") | ||
.delimiter(",") | ||
.query(queryAuthor)); | ||
|
||
String result = new BufferedReader(new InputStreamReader(response.content())) | ||
.lines().collect(Collectors.joining("\n")); | ||
------------------------------------ | ||
|
||
|
||
[discrete] | ||
[[esql-consume-results]] | ||
==== Consume ES|QL results | ||
|
||
The previous example showed that although the raw ES|QL API offers maximum | ||
flexibility, additional work is required in order to make use of the | ||
result data. | ||
|
||
To simplify things, try working with these three main representations of ES|QL | ||
results (each with its own mapping helper): | ||
|
||
* **Objects**, where each row in the results is mapped to an object from your | ||
application domain. This is similar to what ORMs (object relational mappers) | ||
commonly do. | ||
+ | ||
-- | ||
|
||
[source,java] | ||
------------------------------------ | ||
List<Book> queryRes = (List<Book>) client.esql().query(ObjectsEsqlAdapter.of(Book.class), queryAuthor); | ||
|
||
------------------------------------ | ||
-- | ||
* **Cursors**, where you scan the results row by row and access the data using | ||
column names. This is similar to database access libraries. | ||
+ | ||
-- | ||
[source,java] | ||
------------------------------------ | ||
ResultSet resultSet = client.esql().query(ResultSetEsqlAdapter.INSTANCE, queryAuthor); | ||
------------------------------------ | ||
-- | ||
|
||
|
||
[discrete] | ||
[[esql-custom-mapping]] | ||
==== Define your own mapping | ||
|
||
Although the mappers provided by the {java-client} cover many use cases, your | ||
application might require a custom mapping. | ||
You can write your own mapper and use it in a similar way as the | ||
built-in ones. | ||
|
||
Note that mappers are meant to provide a more usable representation of ES|QL | ||
results—not to process the result data. Data processing should be based on | ||
the output of a result mapper. | ||
|
||
Here's an example mapper that returns a simple column-oriented | ||
representation of the data: | ||
|
||
[source,java] | ||
------------------------------------ | ||
public class CustomStringAdapter extends EsqlAdapterBase<String> { | ||
|
||
public static final CustomStringAdapter INSTANCE = new CustomStringAdapter(); | ||
|
||
@Override | ||
public String format() { | ||
return "json"; | ||
} | ||
|
||
@Override | ||
public boolean columnar() { | ||
return true; | ||
} | ||
|
||
@Override | ||
public String deserialize(ApiClient<ElasticsearchTransport, ?> client, QueryRequest request, | ||
BinaryResponse response) | ||
throws IOException { | ||
return new BufferedReader(new InputStreamReader(response.content())) | ||
.lines().collect(Collectors.joining("\n")); | ||
} | ||
} | ||
------------------------------------ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.