We fixed a bug related to numerical filter recently but it involved

!=

operator. I don't think it's applicable to your situation. Were you able to reproduce this issue on a small dataset?