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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
89 Open 1,084 Closed
89 Open 1,084 Closed
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
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

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
15 👎 1
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
@smcvb
24
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
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
@smcvb
13
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
Cache improvements Epic
#641 opened Jul 3, 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
13
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
8
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
4
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
2
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
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
@abuijze @smcvb
10
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
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
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
7
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
@smcvb
10
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
1
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
8
Support SpEL on an @ProcessingGroup annotation equivalent 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.
#1266 opened Nov 6, 2019 by jangalinski
3
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
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
2
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
6
Event Processors Hanging 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.
#3015 opened Apr 22, 2024 by alelkhoury
@abuijze @gklijs
5
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
8
ProTip! no:milestone will show everything without a milestone.