[
https://issues.apache.org/jira/browse/AMQ-9484?focusedWorklogId=916086&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-916086
]
ASF GitHub Bot logged work on AMQ-9484:
---------------------------------------
Author: ASF GitHub Bot
Created on: 23/Apr/24 18:01
Start Date: 23/Apr/24 18:01
Worklog Time Spent: 10m
Work Description: mattrpav commented on PR #1207:
URL: https://github.com/apache/activemq/pull/1207#issuecomment-2073055053
One reason I thought iterating over the index was preferred vs seeking over
the index was to skip over and not include any messages in the ackedAndPrepared
collection.
```
if (ackedAndPrepared != null &&
ackedAndPrepared.contains(entry.getValue().messageId)) {
continue;
}
```
Issue Time Tracking
-------------------
Worklog Id: (was: 916086)
Time Spent: 0.5h (was: 20m)
> Support exporting kahadb messages from a queue with an offset
> -------------------------------------------------------------
>
> Key: AMQ-9484
> URL: https://issues.apache.org/jira/browse/AMQ-9484
> Project: ActiveMQ Classic
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Minor
> Fix For: 6.2.0, 5.18.5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Support exporting and pulling messages from a MessageStore with an offset, to
> prevent loading _every_ message into memory (and subsequent required gc).
> For example, if a user wants to export the last message from a queue with
> 1,000 messages, they can scan over the index skipping most messages vs
> loading all messages into memory to get to the last message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
