Using collection.direct.insert with collection2 and it seems that it is completely bypassing collection2 functionality. Not sure if this is intended behavior but would be nice to just skip the hooks and still have collection2 do validation.
Also when inspecting the record inserted with the direct functionality the record had an ObjectId instead of the string style ID that meteor uses which would lead to a mixed _id type for the collection.
Using collection.direct.insert with collection2 and it seems that it is completely bypassing collection2 functionality. Not sure if this is intended behavior but would be nice to just skip the hooks and still have collection2 do validation.
Also when inspecting the record inserted with the direct functionality the record had an ObjectId instead of the string style ID that meteor uses which would lead to a mixed _id type for the collection.