Is this some thing wrong about operator in.

[Beansprouts]

I have a aql like this(the aql was generated by code,so a little difficult to read):

 for sv_1 in(let r0_2=( for v_2 in concept_class

Filter v_2['_id'] in ["concept_class/40B69814-CF38-966A-0551-979A1A111807"]

SORT v_2['_ShowOrder'] asc 

 return v_2 )

let r1_2=( for v_2 in concept_concrete

Filter v_2['_id'] in ["concept_class/40B69814-CF38-966A-0551-979A1A111807"]

SORT v_2['_ShowOrder'] asc 

 return v_2 )

let r2_2=union(r0_2,r1_2) 

for rp_2 in r2_2 return rp_2)

 for v_1,e_1,p_1 in 1 any sv_1 relation_default filter p_1.edges[0]._type in

 ["concept_class/07A8C5F5-F026-5EA9-BF22-595302AE2CAF",

 "concept_class/8CCFB04F-B2A5-DE5F-1BDF-9319A28AD9CF",

 "concept_class/46BA1A2C-DC16-D2D6-23E8-AB43C52D6F5A",

 "concept_class/87DA9915-24E2-6A9A-DF4B-79C3B48353FD",

 "concept_class/E603D4F1-6048-322D-3E2E-78AD08753805",

 "concept_class/CD1E874F-42B4-D218-2661-88284A3253DE",

 "concept_class/89302181-1EBC-924E-3C22-FF50FD0E4936",

 "concept_class/attributeValue",

 "concept_class/B46B8072-F0A0-9061-D999-C3846DC8CFC0",

 "concept_class/1E7E8940-2E93-22C6-0409-FE03D14D502F",

 "concept_class/398D9BFD-9C4C-4E79-01B3-38583FC5D7D2",

 "concept_class/2BCCF06D-734C-2DFC-E022-332336B044C4",

 "concept_class/F806300A-E483-913F-C71D-EFD99239D718",

 "concept_class/3C5ADB1F-D692-AA46-593C-57B0C4087C6D",

 "concept_class/168F938B-F86B-4012-A9A8-14CAAA3E169B",

 "concept_class/6EEDD594-CE81-DF05-0E9B-3D517FDB884D",

 "concept_class/attributeDefinition",

 "concept_class/123",

 "concept_class/21414276-FB92-4BD9-5F06-9C461A0C0889",

 "concept_class/64FA56EF-DAAF-B3EA-35C9-2DC3BDFE2542",

 "concept_class/1D12485D-EF58-8895-0C32-839114DDEAF9",

 "concept_class/802990F7-398B-F8EC-E23E-04DE7F4CBEEC",

 "concept_class/972860E5-0529-C184-432D-2C9B2C03256E","concept_class/extension"] 

SORT p_1.vertices[length(p_1.vertices)-1]['_ShowOrder'] asc 

 return p_1

Execute the aql above return nothing, just '[]'. But,if i move "concept_class/123" out of the array after in operator, then  i can get the result.

 My arangodb version is 3.0.12 and 3.1.4.

[Jan]

ArangoDB 3.1.4 is more than half a year old.
The problem may have been fixed in the meantime.
Can you retry the query with a recent version of 3.1? The newest version is 3.1.25 at the moment.

Thanks!

[Beansprouts]

Thanks,In ArangoDB 3.2.0 no this problem anymore.

在 2017年7月24日星期一 UTC+8下午7:13:21，Jan写道：

[Jan]

Thanks for confirming it's working in 3.2.
Have you had a chance to try recent versions of 3.1 (e.g. 3.1.25) as well?

Thanks
Jan