Is it possible to configure the FULLTEXT index to create two keys for apostrophed keywords? For example "Juliet's" will be indexed both as "juliet", both as "juliets". Or at least indexed only as "juliet".
Thanks, Riccardo 2014-05-20 10:08 GMT+02:00 Riccardo Tasso <riccardo.ta...@gmail.com>: > Yes it does, > here's the bug report: > https://github.com/orientechnologies/orientdb/issues/2358 > > > 2014-05-20 10:01 GMT+02:00 Artem Orobets <enis...@gmail.com>: > > Hi Riccardo, >> >> Looks like a bug. Probably the reason is an apostrophe, does it works >> with 'chamber' key? >> Could you create a bug >> report<https://github.com/orientechnologies/orientdb/issues/new> >> ? >> >> Best regards, >> Artem Orobets >> >> * Orient Technologiesthe Company behind OrientDB* >> >> >> 2014-05-20 10:53 GMT+03:00 Riccardo Tasso <riccardo.ta...@gmail.com>: >> >> Hi, I'll try to explain briefly what seems a bug to me: >>> >>> I have a hierarchy of classes, but I want a fulltext index (case >>> insensitive) over all of them for the same field "label", here I create: >>> alter property V.label COLLATE ci; >>> create index V-label-fulltext ON V (label) FULLTEXT; >>> >>> Then I try the following test: >>> SELECT FROM index:V-label-fulltext WHERE key = 'juliets' >>> >>> ----+------+-------+------ >>> # |@RID |key |rid >>> ----+------+-------+------ >>> 0 |#-1:-1|juliets|#25:0 >>> 1 |#-1:-1|juliets|#16:22 >>> 2 |#-1:-1|juliets|#16:25 >>> ----+------+-------+------ >>> >>> >>> The first record is: >>> select label, @class from #25:0 >>> >>> ----+-----+----------------+------- >>> # |@RID |label |class >>> ----+-----+----------------+------- >>> 0 |#-2:1|Juliet's chamber|Feature >>> ----+-----+----------------+------- >>> >>> But something doesn't work: >>> SELECT @rid as rid FROM Feature WHERE label containsText 'juliets' >>> >>> 0 item(s) found. Query executed in 0.003 sec(s). >>> >>> >>> The explain says: >>> explain SELECT @rid as rid FROM Feature WHERE label containsText >>> 'juliets' >>> >>> Profiled command >>> '{compositeIndexUsed:1,involvedIndexes:[1],indexReads:3,fullySortedByIndex:false,indexIsUsedInOrderBy:false,current:#16:25,documentAnalyzedCompatibleClass:1,elapsed:0.887353,resultType:collection,resultSize:0}' >>> in 0,001000 sec(s): >>> >>> {"@type":"d","@version":0,"compositeIndexUsed":1,"involvedIndexes":["V-label-fulltext"],"indexReads":3,"fullySortedByIndex":false,"indexIsUsedInOrderBy":false,"current":"#16:25","documentAnalyzedCompatibleClass":1,"elapsed":0.887353,"resultType":"collection","resultSize":0,"@fieldTypes":"compositeIndexUsed=l,involvedIndexes=e,indexReads=l,documentAnalyzedCompatibleClass=l,elapsed=f"} >>> >>> What's wrong? >>> Cheers, >>> Riccardo >>> >>> P.S. I can't use lucene indexing engin by now, I'm sorry >>> >>> -- >>> >>> --- >>> 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 orient-database+unsubscr...@googlegroups.com. >>> 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 orient-database+unsubscr...@googlegroups.com. >> 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
