hiero-ledger / hiero-ledger/hiero-consensus-node

Sub-Records in config data

Open
#13,262 0 comments 0 reactions 1 assignee Claimed by @akugal View on GitHub
Base Config Platform
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

Today I've seen the following config property:

```
@ConfigProperty(defaultValue =
"SEQUENTIAL_THREAD CAPACITY(2) FLUSHABLE UNHANDLED_TASK_METRIC BUSY_FRACTION_METRIC")
TaskSchedulerConfiguration stateHasher
```

Here a `TaskSchedulerConfiguration` should be configured. `TaskSchedulerConfiguration` is a record that looks like this:

```
public record TaskSchedulerConfiguration(
@Nullable TaskSchedulerType type,
@Nullable Long unhandledTaskCapacity,
@Nullable Boolean unhandledTaskMetricEnabled,
@Nullable Boolean busyFractionMetricEnabled,
@Nullable Boolean flushingEnabled,
@Nullable Boolean squelchingEnabled) {}
```

It would be great if we can find a better way to define that configuration. Best would be if every property of the sub-record could be configured individually.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.