>some direct or indirect changes (metadata, rules, validator, etc) >may cause changes to plans around the given RelNode in the downstream >project
Do you think changes like "metadata, rules, validator" can cause "wrong results" issues? What could be the issues caused by "metadata, rules, validator" changes? I know ObjectWeb ASM bytecode manipulation library uses the concepts of versions for quite some time, and it seems to work for them. As you subclass, say, ClassVisitor, you have to pass the API version which your visitor supports. Then ASM fails in the runtime if the visitor happens to be applied with a too recent bytecode. >and gets the source code of the test that he includes into his project and CI Source code and bytecode parsing could be an alternative option (for other cases), however, it is not clear how to tell if the rule in question has been updated to support the new Project/Filter contract. Vladimir
