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
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
updated Apr 26, 2024
OpenTelemetry Issue - Span ended without all scopes!
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.
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
updated Mar 15, 2024
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
updated Mar 15, 2024
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
updated Feb 29, 2024
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
updated Feb 19, 2024
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.
When 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.
EmbeddedEventStore
enables optimizeEventConsumption
(default) it will cause a memory leak of Node
sometimes
Status: Information Required
#2954
opened Jan 4, 2024 by
yitizi
updated Jan 11, 2024
Support Synthetic Flows/Tests
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.
#2950
opened Dec 22, 2023 by
vab2048
updated Dec 27, 2023
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
updated Dec 27, 2023
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
updated Dec 21, 2023
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.
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.
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
updated Dec 18, 2023
Allow parameterized 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.
ResponseType
Priority 3: Could
#1537
opened Oct 13, 2020 by
jnfeinstein
updated Dec 15, 2023
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
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
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
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
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
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
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
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
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
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
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.