Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Montrazul
Yes i found that for console. but i didnt find out how to use it for java api yet Am Dienstag, 20. Mai 2014 15:05:54 UTC+2 schrieb Enrico Risa: > > Yes we have a METADATA field when creating the index and you can pass a > different analyzer. > > As i wrote here, i used the EnglishAnalyzer > > ht

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Enrico Risa
Yes we have a METADATA field when creating the index and you can pass a different analyzer. As i wrote here, i used the EnglishAnalyzer https://github.com/orientechnologies/orientdb-lucene/wiki/Full-Text-Index 2014-05-20 14:20 GMT+02:00 Montrazul : > Will there maybe be an option to configure

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Montrazul
Will there maybe be an option to configure if lucene should use the standardanalyzer or the keyanalyzer? Am Dienstag, 20. Mai 2014 14:14:29 UTC+2 schrieb Artem Orobets: > > Oh sorry, I meant it is not implemented right now. But I've added comment > to the bug to implement it. > > Best regards, >

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Artem Orobets
Oh sorry, I meant it is not implemented right now. But I've added comment to the bug to implement it. Best regards, Artem Orobets * Orient Technologiesthe Company behind OrientDB* 2014-05-20 11:59 GMT+03:00 Riccardo Tasso : > I mean: can I pass to FULLTEXT index some configuration at creation

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Riccardo Tasso
I mean: can I pass to FULLTEXT index some configuration at creation time? I can't see any documentation about it. Thanks, Riccardo 2014-05-20 10:37 GMT+02:00 Artem Orobets : > It seems it is reasonable for all apostrophe usages, so why not > > Best regards, > Artem Orobets > > *Orient Technol

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Artem Orobets
It seems it is reasonable for all apostrophe usages, so why not Best regards, Artem Orobets *Orient Technologies the Company behind OrientDB* 2014-05-20 11:11 GMT+03:00 Riccardo Tasso : > Is it possible to configure the FULLTEXT index to create two keys for > apostrophed keywords? > For exampl

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Riccardo Tasso
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 : > Yes it does, > here's t

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Riccardo Tasso
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 : > Hi Riccardo, > > Looks like a bug. Probably the reason is an apostrophe, does it works with > 'chamber' key? > Could you create a bug > report

Re: [orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Artem Orobets
Hi Riccardo, Looks like a bug. Probably the reason is an apostrophe, does it works with 'chamber' key? Could you create a bug report ? Best regards, Artem Orobets * Orient Technologiesthe Company behind OrientDB* 2014-05-20 10:53 GMT+03

[orientdb] [Orient 1.7.rc2] Bug in fulltext index

2014-05-20 Thread Riccardo Tasso
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