this needs to land in the next major and not 3.7.1. No one will use DT as a property value but they will use it in a traversal and when that is serialized as bytecode the server will fail to know how to deal with it.
On Mon, Sep 18, 2023 at 2:37 PM Valentyn Kahamlyk <valent...@bitquilltech.com.invalid> wrote: > Hi all, > > I implemented the new date functions as described in Dave's proposal > > https://github.com/apache/tinkerpop/blob/master/docs/src/dev/future/proposal-3-remove-closures.asciidoc > . > As part of this task, I added a new data type DT to represent time > intervals such as minute, hour, day. Formally, this is a breaking > change because version 3.7.0 clients will not be able to read data if > DT is used as a property value. I think this is not a viable use case > and suggest merging these changes into 3.7.x rather than creating 3.8 > or 4.0 branches and delay date functions release. > Does anyone have any concerns about including this into 3.7.x? If no > one raises any objections within 72 hours, then I will assume lazy > consensus and merge in my PR > https://github.com/apache/tinkerpop/pull/2223. > > Regards, Valentyn. >
