Index Creation and Document Addition

Question 1

Index Creation

Answer 1

PUT /my_index

Question 2

Add Documents

Answer 2

POST /my_index/_doc/1
{
“name”: “John Doe”,
“age”: 30,
“location”: “New York”
}

Question 3

Basic Search

Answer 3

GET /my_index/_search
{
“query”: {
“match”: {
“name”: “John”
}
}
}

This will return documents in my_index where the name field matches “John”.

Question 4

Match Query

Answer 4

GET /my_index/_search
{
“query”: {
“match”: {
“content”: “Elasticsearch tutorial”
}
}
}

The above query searches for documents where the content field contains terms related to “Elasticsearch tutorial”.

Question 5

Term Query

Answer 5

GET /my_index/_search
{
“query”: {
“term”: {
“status”: “published”
}
}
}

This example searches for documents where the status field exactly matches “published”.

Question 6

Multi Match Query

Answer 6

GET /my_index/_search
{
“query”: {
“multi_match”: {
“query”: “Elasticsearch tutorial”,
“fields”: [“title”, “content”, “tags”]
}
}
}
This query searches for documents where “Elasticsearch tutorial” appears in any of the specified fields (title, content, or tags).

Question 7

Match Phrase Query

Answer 7

GET /my_index/_search
{
“query”: {
“match_phrase”: {
“content”: “quick brown fox”
}
}
}

This query finds documents where the phrase “quick brown fox” appears in the content field, in that exact order.

Question 8

Match All Query

Answer 8

GET /my_index/_search
{
“query”: {
“match_all”: {}
}
}

The match_all query returns all documents in the index. It is often used as a starting point for filtering or sorting the entire data set.

Question 9

Range Query

Answer 9

GET /my_index/_search
{
“query”: {
“range”: {
“publish_date”: {
“gte”: “2023-01-01”,
“lte”: “2023-12-31”
}
}
}
}
This query searches for documents where the publish_date falls within the specified range.

Question 10

Boolean Search

Answer 10

GET /my_index/_search
{
“query”: {
“bool”: {
“must”: [
{ “match”: { “title”: “Elasticsearch” } }
],
“must_not”: [
{ “term”: { “status”: “archived” } }
],
“should”: [
{ “match”: { “tags”: “search” } }
]
}
}
}

In this example:
The must clause requires the title field to contain “Elasticsearch”.
The must_not clause excludes documents where the status is “archived”.
The should clause boosts the relevance of documents that also have “search” in the tags field.

Question 11

Wildcard Query

Answer 11

The wildcard query allows using wildcard characters like * (matches zero or more characters) and ? (matches a single character).
{
“query”: {
“wildcard”: {
“username”: “user*”
}
}
}

Question 12

Prefix Query

Answer 12

{
“query”: {
“prefix”: {
“product”: “ela”
}
}
}

This query finds documents where the product field starts with “ela” (e.g., “elastic”, “elaborate”).

Question 13

Exists

Answer 13

{
“query”: {
“exists”: {
“field”: “tags”
}
}
}

This query retrieves documents that have a non-null tags field.

Question 14

Fuzzy Query

Answer 14

{
“query”: {
“fuzzy”: {
“name”: {
“value”: “elastik”,
“fuzziness”: 2
}
}
}
}

This query finds documents where the name field is similar to “elastik” with up to two character changes.