[ https://issues.apache.org/jira/browse/IGNITE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055637#comment-16055637 ]
Ilya Lantukh commented on IGNITE-5558: -------------------------------------- I think that many of our WAL record types don't make sense outside of scope of ignite node (BTREE_*, META_PAGE_UPDATE_*). Should we consider adding ability to filter out certain record types from such public iterator? > Add ability to read WAL outside of an Ignite node > ------------------------------------------------- > > Key: IGNITE-5558 > URL: https://issues.apache.org/jira/browse/IGNITE-5558 > Project: Ignite > Issue Type: Improvement > Components: cache > Affects Versions: 2.1 > Reporter: Alexey Goncharuk > Fix For: 2.2 > > > Currently, the WAL iterator can be obtained from the WAL manager when an > Ignite node is up and running. > However, it may be extremely useful to read WAL in an 'offline' mode, when a > node is not started up. This may be required for crash analysis or to export > committed data to some external systems. > In the future we can make this even a public interface, however as a starting > point, I would like to keep it in private package because moving to the > public package will require Iterator and records to be public too. > So, as a starting point, we need: > * An object that will allow us to get WALIterator instances (probably, > should be closeable) > * A method on this object which will create an iterator by a file name or > file names > Using this object should not require an active Ignite instance running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)