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

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

EventSourcingRepository API to load an aggregate up to a specific 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.
#1661 opened Jan 4, 2021 by saratry
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
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.
#1590 opened Nov 4, 2020 by smcvb Release 5.0.0
1
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
1
Allow parameterized ResponseType 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.
#1537 opened Oct 13, 2020 by jnfeinstein
5
Provide a fluent API for assertions 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: Feature Use to signal an issue is completely new to the project.
#1476 opened Jul 27, 2020 by OLibutzki
BufferingQueryUpdateEmitter 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.
#1471 opened Jul 22, 2020 by m1l4n54v1c
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
@smcvb
1
Integration test facility to ensure and assert processed events 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.
#1426 opened Apr 30, 2020 by hatzlj
1
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
@smcvb
4
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
3
Improved API for Aggregate State Transitions 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.
#1415 opened Apr 21, 2020 by vab2048
3
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
Improve support for hierarchical Spring application contexts Epic
#1341 opened Feb 11, 2020 by OLibutzki
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
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
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
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
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
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
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
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
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
ProTip! Find all open issues with in progress development work with linked:pr.