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
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 prevention of 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.
@QueryHandlers
when the Event Handling Component backing the query handler is Replaying
Priority 3: Could
#2949
opened Dec 21, 2023 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
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
Table partitioning for event table
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.
#2979
opened Feb 14, 2024 by
williancolognesitrimble
Make forwarding mode configurable for entire Aggregate instead of configuring for each AggregateMember
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.
#474
opened Jan 11, 2018 by
marleinevankampen
Builder pattern improvements
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.
#902
opened Nov 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
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
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
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
TinyLFU-based caching policy
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.
#518
opened Feb 27, 2018 by
ben-manes
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
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
Ordering of event handler instance/type group selectors
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.
#1028
opened Mar 14, 2019 by
m1l4n54v1c
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
Allow Map for ResponseType of a Query
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.
#1257
opened Nov 1, 2019 by
Sam-Kruglov
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
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
Dynamic Configuration Changes
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.
#1276
opened Nov 26, 2019 by
m1l4n54v1c
Improve support for hierarchical Spring application contexts
Epic
#1341
opened Feb 11, 2020 by
OLibutzki
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
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
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-04-18.