Hi Brian, yes it is not intendend. Lucene index shouldn't be used with = operator. I will fix this preventing usage of Lucene index in exact match so it will works as expected.
Enrico 2014-06-26 16:26 GMT+02:00 Brian O'Keefe <[email protected]>: > Hi all, > > I'm experimenting with the new Lucene Index functionality to index a "full > name" field. It seems to work great if using queries such as: > > SELECT FROM Person WHERE name LUCENE '"Thomas" AND "Jones"' -- contains > everyone who is "Thomas Jones", "Jones Thomas", "A. Thomas Jones", etc. -- > as expected > > However, one behavior change that I noticed was if I run the query: > > SELECT FROM Person WHERE name = 'Thomas Jones' > > It will return any person who has either Thomas OR Jones appearing is > his/her name (e.g., 'Thomas Smith', 'Fred Jones'). I would expect an exact > match in this situation. This causes a bit of a confusion for any > end-users running ad-hoc queries. > > If this is functioning as intended, that is fine (and I can educate the > few testing this), but I wanted to raise the issue in case it is not > intentional. > > Thanks, > > Brian > > -- > > --- > 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. > -- --- 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.
