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
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
Implement Page and PageResponseType for QueryBus
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.
#486
opened Jan 29, 2018 by
smcvb
Return position after Append 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.
#1740
opened Mar 22, 2021 by
smcvb
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
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
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
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
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
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
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.
Automatic Aggregate Event Stream filtering
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.
#1589
opened Nov 4, 2020 by
smcvb
Add and enhance JavaDoc for the new Unit of Work
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.
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
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
Aggregate Parameter Resolver
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.
#2399
opened Sep 27, 2022 by
smcvb
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
Configuration Testing
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.
#1640
opened Dec 15, 2020 by
smcvb
Chaining Parameter Resolvers
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.
#1639
opened Dec 15, 2020 by
smcvb
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
ProTip!
Find all open issues with in progress development work with linked:pr.