ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: WAL iterator unexpected behavior
Date Tue, 29 May 2018 17:32:39 GMT

Thanks for initiating the discussion!

I am not sure I understand the issue fully, but in my view we should not
allow iteration through WAL if we cannot deserialize a portion of it. We
must require that ignite-index is in the classpath, so I would just fail
right away with exception.


On Tue, May 29, 2018 at 6:53 AM, Dmitriy Govorukhin <
dmitriy.govorukhin@gmail.com> wrote:

> Igniters,
> I faced a problem with iterate over WAL.
> Let's imagine that we write WAL and write some record which depends from
> ignite-index.
> And then move files to another machine, which does not have ignite-index in
> the classpath.
> Now try to iterate over WAL.
> If iterator can not deserialize some record he try to go next and
> execute advanceSegment() for switching to the next segment.
> (ignite-index not in the classpath)
> 1. Iterator skips part of the WAL because advanceRecord() failed to
> deserialize record.
> 2. Iterator does not signal that there was an error.
> In my opinion, it is not that we expected.
> Any comments?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message