}
    }

    @Test
    public void testScrollSearch_customAccumulator() {
        createTestIndex();
        indexDocuments(5);
        runner.refresh();

        // Use custom accumulator to sum values
        List<Integer> values = new ArrayList<>();
        List<Integer> results = ScrollOperationHelper.scrollSearch(client, suggester.settings(), INDEX_NAME, QueryBuilders.matchAllQuery(),

## Um aplicativo com callbacks { #an-app-with-callbacks }

Vamos ver tudo isso com um exemplo.

Imagine que você desenvolve um aplicativo que permite criar faturas.

Essas faturas terão um `id`, `title` (opcional), `customer` e `total`.

O usuário da sua API (um desenvolvedor externo) criará uma fatura na sua API com um request POST.

Então sua API irá (vamos imaginar):

* Enviar a fatura para algum cliente do desenvolvedor externo.

}

// Option is a function type that accepts a pointer Target
type Option func(*KeycloakProvider)

// WithTransport provide custom transport
func WithTransport(transport http.RoundTripper) Option {
	return func(p *KeycloakProvider) {
		p.client = http.Client{
			Transport: transport,
		}
	}
}

second intervals between attempts $MC_COMMAND ; STATUS=$? ; done ; set -e ; # reset `e` as active return 0 } # runCommand ($@) # Run custom mc command runCommand() { ${MC} "$@" return $? } # Try connecting to MinIO instance {{- if .Values.tls.enabled }} scheme=https {{- else }} scheme=http {{- end }} connectToMinio $scheme {{ if .Values.customCommands }} # Run custom commands {{- range .Values.customCommands }} runCommand {{ .command }} {{- end }} {{- end }} minio/templates/_helper_policy.tpl {{-...

            assertEquals(Trans2QueryPathInformationResponse.SMB_QUERY_FILE_STANDARD_INFO, infoLevel.getInt(resp));
        }

        @Test
        @DisplayName("Should initialize with custom information level")
        void testConstructorWithCustomLevel() throws Exception {
            int customLevel = 0x200;
            Trans2QueryPathInformationResponse resp = new Trans2QueryPathInformationResponse(customLevel);

Uno de los casos de uso principales sería transmitir `bytes` en lugar de strings; por supuesto puedes hacerlo.

{* ../../docs_src/stream_data/tutorial001_py310.py ln[44:47] hl[47] *}

## Un `PNGStreamingResponse` personalizado { #a-custom-pngstreamingresponse }

En los ejemplos anteriores, se transmitieron los bytes de datos, pero la response no tenía un header `Content-Type`, así que el cliente no sabía qué tipo de datos estaba recibiendo.

<img src="/img/tutorial/additional-responses/image01.png">

## Комбінуйте попередньо визначені та власні відповіді { #combine-predefined-responses-and-custom-ones }

Можливо, ви захочете мати кілька попередньо визначених відповідей, що застосовуються до багатьох операцій шляху, але поєднувати їх із власними відповідями, потрібними для кожної операції шляху.

		"x-minio-origin-endpoint": func() string {
			if globalMinioEndpoint != "" {
				return globalMinioEndpoint
			}
			return getAPIEndpoints()[0]
		}(), // MinIO specific custom elements.
	}

	// Add deployment as part of response elements.
	respElements["x-minio-deployment-id"] = globalDeploymentID()
	if args.RespElements["content-length"] != "" {

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...