Issues: AxonFramework/AxonFramework
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
QueryUpdateEmitter should return a number of affected queries
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Under Discussion
Use to signal that the issue in question is being discussed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#1470
opened Jul 22, 2020 by
m1l4n54v1c
updated Sep 7, 2023
Logging Suggestion
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#1424
opened Apr 28, 2020 by
Sam-Kruglov
updated Sep 7, 2023
Add support for Quarkus
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Type: Feature
Use to signal an issue is completely new to the project.
#1318
opened Jan 15, 2020 by
tunovic
updated Sep 7, 2023
Support SpEL on an Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
@ProcessingGroup
annotation equivalent
Priority 4: Would
#1266
opened Nov 6, 2019 by
jangalinski
updated Sep 6, 2023
Provide SQL for all Entities
Ideal for Contribution
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
#1258
opened Nov 2, 2019 by
jangalinski
updated Sep 6, 2023
Granular Axon Starter "use case" selection
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Feature
Use to signal an issue is completely new to the project.
#1256
opened Oct 29, 2019 by
jangalinski
updated Sep 6, 2023
Projection Testing
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Type: Feature
Use to signal an issue is completely new to the project.
#729
opened Aug 23, 2018 by
m1l4n54v1c
updated Sep 6, 2023
Allow configuration of a processing group's type through the annotation.
Status: Under Discussion
Use to signal that the issue in question is being discussed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2788
opened Jul 22, 2023 by
vab2048
updated Jul 25, 2023
Except-Logic for DisallowReplay annotation
Status: Under Discussion
Use to signal that the issue in question is being discussed.
Type: Feature
Use to signal an issue is completely new to the project.
#2775
opened Jul 4, 2023 by
nils-christian
updated Jul 10, 2023
Aggregate snapshotter stops working
Status: Information Required
Use to signal this issue is waiting for information to be provided in the issue's description.
Type: Question
Use to signal the issue is a question of how the project works and thus does not require development
#2770
opened Jun 27, 2023 by
unisteven
updated Jun 27, 2023
Upcasters are not applied to DeadLetterQueue entries
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Type: Feature
Use to signal an issue is completely new to the project.
#2500
opened Nov 23, 2022 by
nils-christian
updated Jun 27, 2023
Add create/delete context operations to the Low priority. Issues that are nice to have but have a straightforward workaround.
Status: In Progress
Use to signal this issue is actively worked on.
Type: Feature
Use to signal an issue is completely new to the project.
AxonServerContainer
Priority 3: Could
#2764
opened Jun 21, 2023 by
smcvb
updated Jun 21, 2023
Set initial token to head when all contained Event Handling Components of a Streaming Event Processor disallow replays
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
#2760
opened Jun 20, 2023 by
smcvb
updated Jun 20, 2023
Live Replay
Status: Under Discussion
Use to signal that the issue in question is being discussed.
Type: Feature
Use to signal an issue is completely new to the project.
#2740
opened Jun 8, 2023 by
bavodaniels
updated Jun 16, 2023
Distinct Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
Repository
beans based on configured Aggregate type
Priority 4: Would
#1688
opened Jan 22, 2021 by
gsteen
updated Jun 12, 2023
AggregateLifecycle.createNew does not return Entity ID in CommandResultMessage
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
#2059
opened Dec 22, 2021 by
jasperfect
updated Jun 12, 2023
Enable tracing in DisruptorCommandBus with SpanFactory
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Feature
Use to signal an issue is completely new to the project.
#2402
opened Sep 27, 2022 by
smcvb
updated Jun 12, 2023
Interceptor list Spring auto configuration
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
Type: Feature
Use to signal an issue is completely new to the project.
#1422
opened Apr 24, 2020 by
smcvb
updated Jun 12, 2023
AggregateTestFixture does not validate deadlines set in the past
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2460
opened Oct 27, 2022 by
CodeDrivenMitch
updated Jun 12, 2023
Allow for customization of queries in the Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
JdbcTokenStore
Priority 3: Could
#2410
opened Sep 29, 2022 by
trimoq
updated Jun 12, 2023
Add the abilty to fail on unresolved deadline handlers
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2334
opened Aug 19, 2022 by
YvonneCeelie
updated Jun 12, 2023
Rethink SnapshotFilter usage
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#1769
opened Apr 26, 2021 by
smcvb
updated Jun 12, 2023
Graceful recovery from broken connections - MultiStreamableMessageSource
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Type: Feature
Use to signal an issue is completely new to the project.
#1327
opened Jan 22, 2020 by
smcvb
updated Jun 12, 2023
Improved API for Aggregate State Transitions
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Type: Feature
Use to signal an issue is completely new to the project.
#1415
opened Apr 21, 2020 by
vab2048
updated May 5, 2023
Expose total bus capacity as metric
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Under Discussion
Use to signal that the issue in question is being discussed.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2677
opened Apr 6, 2023 by
CodeDrivenMitch
updated Apr 12, 2023
ProTip!
Follow long discussions with comments:>50.