## 요약

`Query`, `Path`(아직 보지 못한 다른 것들도)를 사용하면 [쿼리 매개변수와 문자열 검증](query-params-str-validations.md){.internal-link target=_blank}에서와 마찬가지로 메타데이터와 문자열 검증을 선언할 수 있습니다.

그리고 숫자 검증 또한 선언할 수 있습니다:

* `gt`: 크거나(`g`reater `t`han)
* `ge`: 크거나 같은(`g`reater than or `e`qual)
* `lt`: 작거나(`l`ess `t`han)
* `le`: 작거나 같은(`l`ess than or `e`qual)

/// info | 정보

`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.

///

/**
 * Response object for faceted search results containing query counts and field facets.
 * This class processes OpenSearch aggregations to provide structured facet information
 * for search result filtering and navigation.
 */
public class FacetResponse {
    /**
     * Map containing query facet counts, where keys are decoded query strings
     * and values are document counts for each query.
     */

import org.codelibs.fess.util.ComponentUtil;
import org.lastaflute.core.message.UserMessages;
import org.opensearch.index.query.QueryBuilder;
import org.opensearch.index.query.QueryBuilders;
import org.opensearch.index.query.RangeQueryBuilder;

/**
 * Command class for handling term range query execution and conversion.
 * This class processes Lucene TermRangeQuery objects and converts them to OpenSearch QueryBuilder instances.
 */

 * list is a single empty string: `[""]`.
 *
 * ### Query
 *
 * The query is optional: it can be null, empty, or non-empty. For many HTTP URLs the query string
 * is subdivided into a collection of name-value parameters. This class offers methods to set the
 * query as the single string, or as individual name-value parameters. With name-value parameters

        });

        String query = ComponentUtil.getQueryStringBuilder().params(params).sortField(params.getSort()).build();
        List<Map<String, Object>> documentItems;
        try {
            documentItems = searchInternal(query, params, userBean);
        } catch (final InvalidQueryException e) {
            if (logger.isDebugEnabled()) {
                logger.debug("Invalid query: {}", query, e);
            }

{* ../../docs_src/path_params_numeric_validations/tutorial006_an_py39.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){.internal-link target=_blank}.

And you can also declare numeric validations:

* `gt`: `g`reater `t`han

        QueryContext context = new QueryContext("*:*", false);
        MatchAllDocsQuery query = new MatchAllDocsQuery();
        float boost = 1.0f;

        QueryBuilder result = matchAllQueryCommand.execute(context, query, boost);

        assertNotNull(result);
        assertTrue(result instanceof MatchAllQueryBuilder);

        // Verify the query builder generates correct JSON

        QueryContext context = new QueryContext("test", false);
        TermRangeQuery query = new TermRangeQuery("title", new BytesRef("aaa"), new BytesRef("zzz"), true, true);

        QueryBuilder builder = queryCommand.convertTermRangeQuery(context, query, 1.0f);
        assertNotNull(builder);
        assertTrue(builder instanceof RangeQueryBuilder);

        // Query was processed successfully
        RangeQueryBuilder rqb = (RangeQueryBuilder) builder;

        return getComponent(SAMBA_HELPER);
    }

    /**
     * Gets the query helper component.
     * @return The query helper.
     */
    public static QueryHelper getQueryHelper() {
        return getComponent(QUERY_HELPER);
    }

    /**
     * Gets the query field configuration.
     * @return The query field config.
     */
    public static QueryFieldConfig getQueryFieldConfig() {