Skip to content

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
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort

Issues list

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
Various issues when importing Axon in Eclipse 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.
#2865 opened Oct 11, 2023 by nils-christian Release 4.10.0
When EmbeddedEventStore enables optimizeEventConsumption (default) it will cause a memory leak of Node sometimes Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Type: Bug Use to signal issues that describe a bug within the system.
#2954 opened Jan 4, 2024 by yitizi
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.
#2966 opened Jan 24, 2024 by smcvb Release 5.0.0
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
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
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
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
Contract Testing 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.
#2990 opened Feb 28, 2024 by meierw
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
Allow prevention of @QueryHandlers when the Event Handling Component backing the query handler is Replaying 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.
#2949 opened Dec 21, 2023 by smcvb
ProTip! Add no:assignee to see everything that’s not assigned.