{* ../../docs_src/query_params_str_validations/tutorial014_an_py310.py hl[10] *}

## Custom Validation { #custom-validation }

There could be cases where you need to do some **custom validation** that can't be done with the parameters shown above.

In those cases, you can use a **custom validator function** that is applied after the normal validation (e.g. after validating that the value is a `str`).

 * <p>
 * Qualifiers are used to distinguish between multiple beans of the same type,
 * allowing for more precise control over which implementation should be injected.
 * Custom qualifier annotations should be annotated with {@code @Qualifier}.
 * <p>
 * Example of creating a custom qualifier:
 * <pre>
 * {@literal @}Qualifier
 * {@literal @}Retention(RUNTIME)
 * public @interface Database {
 *     String value();
 * }
 * </pre>
 *

    }

    @Test
    public void test_addSearchLog_accessType_customLlmName() {
        final SearchLog searchLog = callCreateSearchLogAndGetResult("my-custom-llm");
        assertEquals("my-custom-llm", searchLog.getAccessType());
    }

    @Test
    public void test_addSearchLog_accessType_blankStringDefaultsToWeb() {
        final SearchLog searchLog = callCreateSearchLogAndGetResult("");

 * provided by Maven and custom types registered through SPI provider implementations.
 *
 * @since 4.0.0
 */
@Experimental
public interface TypeRegistry extends ExtensibleEnumRegistry<Type> {

    /**
     * Obtain the {@link Type} from the specified {@code id}.
     * If no type is known for {@code id}, the registry will
     * create a custom {@code Type} for it.
     *

          {{- if .Values.customCommandJob.exitCommand }}
          command: [ "/bin/sh", "-c" ]
          args: [ "/bin/sh /config/custom-command; EV=$?; {{ .Values.customCommandJob.exitCommand }} && exit $EV" ]
          {{- else }}
          command: [ "/bin/sh", "/config/custom-command" ]
          {{- end }}
          env:
            - name: MINIO_ENDPOINT
              value: {{ template "minio.fullname" . }}

{* ../../docs_src/middleware/tutorial001_py310.py hl[8:9,11,14] *}

/// tip | Consejo

Ten en cuenta que los custom proprietary headers se pueden añadir [usando el prefijo `X-`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers).

      }
    },
    "analyzer": {
      "sv_analyzer": {
        "type": "custom",
        "tokenizer": "standard",
        "filter": ["lowercase", "swedish_stop", "swedish_stemmer"]
      }
    }
  }
}
```

### 2. Add Custom Dictionaries (Optional)

Create custom dictionary files in: `${fess.dictionary.path}/[lang]/`

Available dictionary types:

   *
   * <p>Subclasses can override this method to provide custom equality.
   */
  @Override
  public boolean equals(@Nullable Object obj) {
    return super.equals(obj);
  }

  /**
   * By default delegates to {@link Object#hashCode}. The dynamic proxies' {@code hashCode()} will
   * delegate to this method. Subclasses can override this method to provide custom equality.
   */
  @Override
  public int hashCode() {

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

## A Custom `PNGStreamingResponse` { #a-custom-pngstreamingresponse }

In the examples above, the data bytes were streamed, but the response didn't have a `Content-Type` header, so the client didn't know what type of data it was receiving.

You can create a custom sub-class of `StreamingResponse` that sets the `Content-Type` header to the type of data you're streaming.

        assertNotNull(ioException);
        assertTrue(ioException.getCause() instanceof java.io.IOException);

        // Test with custom exception
        Throwable customCause = new FessSystemException("Custom Fess error");
        GsaConfigException customException = new GsaConfigException("GSA custom error", customCause);
        assertNotNull(customException);
        assertTrue(customException.getCause() instanceof FessSystemException);