/**
     * Searches documents using a Fess query.
     *
     * @param query the Fess query string
     * @return the list of search result documents
     */
    protected List<Map<String, Object>> searchWithQuery(final String query) {
        return searchWithQueryAndMetadata(query).getDocuments();
    }

    private ChatSearchResult searchWithQueryAndMetadata(final String query) {

    response = client.get("/main-depends/")
    assert response.status_code == 422
    assert response.json() == {
        "detail": [
            {
                "type": "missing",
                "loc": ["query", "q"],
                "msg": "Field required",
                "input": None,
            }
        ]
    }


def test_main_depends_q_foo():
    response = client.get("/main-depends/?q=foo")

{* ../../docs_src/path_params_numeric_validations/tutorial006_an_py310.py hl[13] *}

## Recap { #recap }

With `Query`, `Path` (and others you haven't seen yet) you can declare metadata and string validations in the same ways as with [Query Parameters and String Validations](query-params-str-validations.md).

And you can also declare numeric validations:

* `gt`: `g`reater `t`han
* `ge`: `g`reater than or `e`qual

{* ../../docs_src/background_tasks/tutorial002_an_py310.py hl[13,15,22,25] *}

Neste exemplo, as mensagens serão escritas no arquivo `log.txt` *após* o envio da resposta.

Se houver uma query na request, ela será registrada em uma tarefa em segundo plano.

E então outra tarefa em segundo plano gerada na *função de operação de rota* escreverá uma mensagem usando o parâmetro de path `email`.

        // Test with non-phrase query - should throw InvalidQueryException
        Query termQuery = new TermQuery(new Term("field", "value"));
        QueryContext context = new QueryContext("test", false);

        try {
            queryCommand.execute(context, termQuery, 1.0f);
            fail("Should throw InvalidQueryException for non-phrase query");
        } catch (InvalidQueryException e) {

但請記得，當你從 `fastapi` 匯入 `Query`、`Path`、`Header` 等時，它們其實是會回傳特殊類別的函式。

///

/// info | 說明

要宣告標頭，必須使用 `Header`，否則參數會被解讀為查詢參數。

///

## 自動轉換 { #automatic-conversion }

在 `Path`、`Query`、`Cookie` 提供的功能之上，`Header` 還有一些額外的小功能。

大多數標準標頭的單字以連字號（減號，`-`）分隔。

但像 `user-agent` 這樣的變數名稱在 Python 中是無效的。

因此，`Header` 會在預設情況下把參數名稱中的底線（`_`）轉換為連字號（`-`），以便讀取並在文件中顯示該標頭。

                                "required": True,
                                "schema": {"title": "Level1", "type": "string"},
                                "name": "level1",
                                "in": "query",
                            }
                        ],
                        "responses": {
                            "200": {
                                "description": "Successful Response",

import org.opensearch.index.query.BoolQueryBuilder;
import org.opensearch.index.query.Operator;
import org.opensearch.index.query.QueryBuilder;
import org.opensearch.index.query.QueryBuilders;
import org.opensearch.search.SearchHit;
import org.opensearch.transport.client.Client;

/**
 * Internal operations class for deletion functionality.
 * Handles deletion of suggest items by ID, query, or kind.
 *

`Header` is a "sister" class of `Path`, `Query` and `Cookie`. It also inherits from the same common `Param` class.

But remember that when you import `Query`, `Path`, `Header`, and others from `fastapi`, those are actually functions that return special classes.

///

/// info

To declare headers, you need to use `Header`, because otherwise the parameters would be interpreted as query parameters.

///

        searchRenderData.setSearchQuery("");
        assertEquals("", searchRenderData.getSearchQuery());

        // Test with simple query
        searchRenderData.setSearchQuery("test query");
        assertEquals("test query", searchRenderData.getSearchQuery());

        // Test with complex query
        String complexQuery = "title:\"test document\" AND content:search OR category:technology";