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
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
Distributed Query Bus
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.
#613
opened Jun 5, 2018 by
smcvb
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
Improve support for a local event store
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.
#1342
opened Feb 11, 2020 by
OLibutzki
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
Allow asynchronous code in Sagas
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: On Hold
Use to signal that work on this issue is paused. The description should clarify why.
Type: Feature
Use to signal an issue is completely new to the project.
#1860
opened Jul 2, 2021 by
cjdxhjj
Allow for Ephemeral Events
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Type: Feature
Use to signal an issue is completely new to the project.
#1121
opened Jun 11, 2019 by
Blackdread
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
High memory usage when large gaps appear in event store
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.
#1241
opened Oct 9, 2019 by
sgrimm
Introduce Federated/Hierarchical CommandBus
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.
#1092
opened May 15, 2019 by
smcvb
Consistency gap in conjunction with state-stored aggregates
Status: Under Discussion
Use to signal that the issue in question is being discussed.
#1103
opened May 27, 2019 by
OLibutzki
Aggregate Stream Refactoring Support
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Type: Feature
Use to signal an issue is completely new to the project.
Enhancing metric observability
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
#2791
opened Aug 1, 2023 by
CodeDrivenMitch
Alias/Business Name for an Event
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.
#722
opened Aug 20, 2018 by
m1l4n54v1c
Allow registration of Upcasters on all components that do serialization of messages
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.
#746
opened Sep 3, 2018 by
abuijze
Snapshot Warm-Up Service
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.
#1641
opened Dec 15, 2020 by
smcvb
State-Stored Aggregate: AggregateIdentifier has to be String
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.
#1062
opened Apr 18, 2019 by
OLibutzki
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
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
Starting a Saga conditionally
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.
#1900
opened Jul 26, 2021 by
OLibutzki
Health Indicator for Event Processors
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.
#2138
opened Mar 17, 2022 by
smcvb
Testing command, event and aggregate (de)serialization
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.
#1904
opened Aug 5, 2021 by
maartenjanvangool
Custom Scopes
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.
#626
opened Jun 21, 2018 by
m1l4n54v1c
Fix some static analysis findings
Ideal for Contribution
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.
#2594
opened Feb 8, 2023 by
timtebeek
2 of 4 tasks
Allow custom event validation implementations in the ResultValidator
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.
#2429
opened Oct 7, 2022 by
fernanfs
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-04-13.