Hi,

I am getting IO tests failures on 3.3.0.

Sqlg has a SimpleModule which add serializers for its custom id.

    SqlgSimpleModule() {
        super("custom");
//        addSerializer(RecordId.class, new RecordId.RecordIdJacksonSerializerV2d0()); //        addDeserializer(RecordId.class, new RecordId.RecordIdJacksonDeserializerV2d0()); //        addSerializer(SchemaTable.class, new SchemaTable.SchemaTableIdJacksonSerializerV2d0()); //        addDeserializer(SchemaTable.class, new SchemaTable.SchemaTableIdJacksonDeserializerV2d0());

        addSerializer(RecordId.class, new RecordId.RecordIdJacksonSerializerV3d0());         addDeserializer(RecordId.class, new RecordId.RecordIdJacksonDeserializerV3d0());         addSerializer(SchemaTable.class, new SchemaTable.SchemaTableJacksonSerializerV3d0());         addDeserializer(SchemaTable.class, new SchemaTable.SchemaTableJacksonDeserializerV3d0());
    }

How is it suppose to distinguish between v2 and v3?

An example of a failure is 'IoEdgeTest.shouldReadWriteEdge'

If ...V2d0.. is added to the serializers then 'graphson-v3' fails.
If ...V3d0.. is added to the serializers then 'graphson-v2' fails.

TinkerPop's own CustomId tests do not rely on default behavior and manually creates SimpleModules for each scenario.

Are they both suppose to work somehow?

Thanks
Pieter

Reply via email to