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
90 Open 1,085 Closed
90 Open 1,085 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

Distinct Repository beans based on configured Aggregate type 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.
#1688 opened Jan 22, 2021 by gsteen updated Jun 12, 2023
3
Live Replay 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.
#2740 opened Jun 8, 2023 by bavodaniels updated Jun 16, 2023
@smcvb @bavodaniels
6
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 updated Jun 20, 2023
Add create/delete context operations to the AxonServerContainer Priority 3: Could 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.
#2764 opened Jun 21, 2023 by smcvb updated Jun 21, 2023
@smcvb
Upcasters are not applied to DeadLetterQueue entries 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.
#2500 opened Nov 23, 2022 by nils-christian updated Jun 27, 2023
@gklijs
6
Aggregate snapshotter stops working Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#2770 opened Jun 27, 2023 by unisteven updated Jun 27, 2023
@unisteven
1
Except-Logic for DisallowReplay annotation 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.
#2775 opened Jul 4, 2023 by nils-christian updated Jul 10, 2023
@CodeDrivenMitch
3
Allow configuration of a processing group's type through the annotation. 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.
#2788 opened Jul 22, 2023 by vab2048 updated Jul 25, 2023
@vab2048
4
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 updated Sep 6, 2023
8
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 updated Sep 6, 2023
@smcvb
10
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 updated Sep 6, 2023
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 updated Sep 6, 2023
3
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 updated Sep 7, 2023
15
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 updated Sep 7, 2023
@smcvb
4
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 updated Sep 7, 2023
@smcvb
1
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 updated Sep 7, 2023
Use PostgresTokenTableFactory when using H2 in PostgresSQL mode 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.
#1891 opened Jul 20, 2021 by mikelhamer updated Sep 7, 2023
@mikelhamer
6
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 updated Sep 7, 2023
unexpected database load with JpaEventStorageEngine::fetchEvents ramping up Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#2641 opened Mar 13, 2023 by junkdog updated Sep 7, 2023
@junkdog
3
Make gapless tokens possible on JDBC/JPA databases 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.
#2747 opened Jun 13, 2023 by hjohn updated Sep 15, 2023
@hjohn @smcvb
12
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 updated Oct 16, 2023
@CodeDrivenMitch
1
Support for Virtual Threads - JDK21 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.
#2710 opened May 14, 2023 by mjagus updated Oct 18, 2023
4
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 updated Nov 22, 2023
2 of 4 tasks
7
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 updated Nov 28, 2023
3
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 updated Dec 15, 2023
5
ProTip! Follow long discussions with comments:>50.