Hello, I have experienced the following today, could someone else try it out?
I have a vertex, with a string property: externalID. It has this kind of content: "37256", "1667556" etc.. If I put a Lucene fulltext index on the field, the following query throws an IndexOutOfBoundException: *select @rid, externalID from User where externalID in [166734]* Even if I add quotes around it. It's interesting that if I issue the following: *select @rid, externalID from User where externalID in [" 1 66734" ]* It will fill up the externalID value of the results with 66734 for the first record (it's a real one) and 1 for the rest (these does not exist). If I change the index to a full text hash index, the IN querying works perfectly. Could someone verify that it's a bug? If so, I will open up a case. Thanks, Aron -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
