Yeah, currently sequence date type internally used is long type and it seems not flexible enough to deal with existing sequence type not compatible. Not sure whether overcoming the limitation is on the radar given that currently team is busy with v6 implementation.