Configuration

Qubit provides build-time configuration for scanning, code generation, and logging.

Scanning

By default, Qubit scans all application classes for lambda queries. For large applications, configure a package allowlist to skip framework classes:

# Only scan classes in these packages (allowlist mode)
quarkus.qubit.scanning.include-packages=com.example.

Multiple packages:

quarkus.qubit.scanning.include-packages=com.example.api.,com.example.service.,com.example.domain.

When configured, Qubit skips scanning of framework classes (Narayana, Mutiny, Vert.x, Netty, etc.), reducing discovery phase time.

Other scanning options:

Property Default Description

quarkus.qubit.scanning.exclude-packages

java.,jakarta.

Package prefixes to exclude from scanning

quarkus.qubit.scanning.include-packages

(not set)

Package allowlist (when set, ONLY these packages are scanned)

quarkus.qubit.scanning.scan-test-classes

true

Whether to scan integration test classes (.it., .test. paths)

Code Generation

Property Default Description

quarkus.qubit.generation.class-name-prefix

QueryExecutor_

Prefix for generated executor class names

quarkus.qubit.generation.target-package

io.quarkiverse.qubit.generated

Package for generated executor classes

Logging

The log level for Qubit uses the standard Quarkus logging category:

quarkus.log.category."io.quarkiverse.qubit".level=DEBUG

Additional fine-grained logging switches:

Property Default Description

quarkus.qubit.logging.log-scanned-classes

false

Log each scanned class (very verbose)

quarkus.qubit.logging.log-generated-classes

true

Log each generated executor class

quarkus.qubit.logging.log-deduplication

false

Log lambda deduplication events

quarkus.qubit.logging.log-bytecode-analysis

false

Log detailed bytecode analysis steps

Analysis

Property Default Description

quarkus.qubit.fail-on-analysis-error

true

Whether to fail the build when bytecode analysis encounters an error. When false, unsupported patterns are logged and skipped.