Problem with lambda based predicate is that it is not possible to resolve previous row builder definition when row uses predicate as row id. It is important to be able to find previous row builders in order to correctly validate against row spans at table definition time.
Additionally using literal index row predicates with sets of valid index ranges and range set materialization support - will allow to create internal association of index to row definition that will speed up row resolving (for new row insertions no additional lambda evaluation will be required as long as index to rowDef map is available)
Problem with lambda based predicate is that it is not possible to resolve previous row builder definition when row uses predicate as row id. It is important to be able to find previous row builders in order to correctly validate against row spans at table definition time. Additionally using literal index row predicates with sets of valid index ranges and range set materialization support - will allow to create internal association of index to row definition that will speed up row resolving (for new row insertions no additional lambda evaluation will be required as long as index to rowDef map is available)