What is the expected behavior when Go over multiple edgeTypes, but filter is applied to one edgeType

[critical27]

create edge e1(p1 int)
insert edge e1(p1) values 1 -> 1:(1)
insert edge e1(p1) values 1 -> 2:(2)
insert edge e1(p1) values 1 -> 3:(3)
insert edge e1(p1) values 1 -> 4:(4)
insert edge e1(p1) values 1 -> 5:(5)

create edge e2(p1 int)
insert edge e2(p1) values 1 -> 1:(1)

go from 1 over e1, e2 where e1.p1 > 3

What is the expected behavior when Go over multiple edgeTypes, but filter is applied to one edgeType?

go from 1 over e1, e2 where e1.p1 > 3 || e2.p1 > 0

Result of this query make more sense.

[critical27]

IMO, we should return edges of e1 which can pass filter and all edges of e2. Also I think the filter in our interface, should only applied to one edge type. However, we could support filter in each edgeTypes. For example, sth like:

go from 1 over e1 (where e1.p1 > 3), e2 (where e2.p1 > 0)

[amber-moe]

Good point. Will update the doc when this issue is addressed.

[CPWstatic]

As we discussed offline, the existing behavior is in line with expectations.