}
    }

    public void test_complex_query_strings() {
        // Test various complex query strings
        String[] queryStrings = { "title:test", "content:\"quoted value\"", "field:value AND other:value", "field:value OR other:value",
                "field:[1 TO 100]", "field:value*", "field:?value", "field:~value", "field:value^2", "タイトル:テスト", "标题:测试", "제목:테스트" };

    * Otro ejemplo sería `201`, "Created". Comúnmente se usa después de crear un nuevo registro en la base de datos.
    * Un caso especial es `204`, "No Content". Este response se usa cuando no hay contenido para devolver al cliente, por lo tanto, el response no debe tener un body.

	}

	_, err := objectAPI.GetBucketInfo(ctx, bucketName, BucketOptions{})
	if err != nil {
		writeErrorResponse(ctx, w, toAPIError(ctx, err), r.URL)
		return
	}

	// PutBucketNotification always needs a Content-Length.
	if r.ContentLength <= 0 {
		writeErrorResponse(ctx, w, errorCodes.ToAPIErr(ErrMissingContentLength), r.URL)
		return
	}

	}

	// Initialize erasure metadata.
	for index := range partsMetadata {
		partsMetadata[index] = fi
	}

	// Guess content-type from the extension if possible.
	if userDefined["content-type"] == "" {
		userDefined["content-type"] = mimedb.TypeByExtension(path.Ext(object))
	}

	// if storageClass is standard no need to save it as part of metadata.

    /**
     * Download the protected words file for the specified dictionary.
     *
     * @param dictId identifier of the dictionary
     * @param body download request payload
     * @return stream response with file content
     */
    // GET /api/admin/dict/protwords/download/{dictId}
    @Execute
    public StreamResponse get$download(final String dictId, final DownloadBody body) {
        body.dictId = dictId;

        // Query was processed successfully

        // Test with multiple wildcards
        QueryContext queryContext2 = new QueryContext("*te*st*", false);
        WildcardQuery wildcardQuery2 = new WildcardQuery(new Term("content", "*te*st*"));

        QueryBuilder queryBuilder2 = queryCommand.convertWildcardQuery(queryContext2, wildcardQuery2, 1.0f);
        assertNotNull(queryBuilder2);

import org.codelibs.fess.util.SearchEngineUtil.XContentBuilderCallback;
import org.lastaflute.di.exception.IORuntimeException;
import org.opensearch.common.xcontent.XContentType;
import org.opensearch.core.xcontent.MediaType;
import org.opensearch.core.xcontent.ToXContent;
import org.opensearch.core.xcontent.XContentBuilder;
import org.opensearch.search.SearchHit;

public class SearchEngineUtilTest extends UnitFessTestCase {

direct YAML support in the API available today), the Content-Type and Accept
headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a

    }

    public void test_constructor_withLongMessage() {
        // Test with long message
        StringBuilder sb = new StringBuilder();
        for (int i = 0; i < 1000; i++) {
            sb.append("Long message content ");
        }
        String longMessage = sb.toString();
        ResultOffsetExceededException exception = new ResultOffsetExceededException(longMessage);

        assertEquals(longMessage, exception.getMessage());

                "operationId": "read_items_items__get",
                "responses": {
                    "200": {
                        "description": "Successful Response",
                        "content": {
                            "application/json": {
                                "schema": {}
                            }
                        }
                    }
                },