replication with archive engine

[Darin Shintani]

This scenario is on v 5.1.48

I have a master db with a table using myisam. I have the same table using the archive engine on a slave db. My understanding is that the archive engine does not allow UPDATE and DELETE statements. When I run a DELETE statement against the master db table, the slave tries to execute that DELETE statement, but receives an Error 1031 (Table storage engine doesn't have this option) and the slave stops replicating. Shouldn't the slave filter the statements? Did I miss some configuration?

I was able to get around it by adding slave-skip-errors=1031, however, that does not seem to be the correct solution.

Thanks,
Darin