Open pedro93 opened 3 years ago
Changing the existing field in schema is backward-incompatible change, thus causing this exception. When server throw such exceptions, it should drop the segment and try to download a new one from the deep storage, then it should auto recover
Hello,
As discussed in this slack thread there seems to be a bug in Pinot v0.7.1 where updating the default value of an existing dimension field of type String in a Schema will through an exception of this sort:
The concrete change in question was from:
to:
This pinot instance already had existing segments in the servers with a backup in deep storage and as such I had triggered a segment reload.
Thank you.