Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread syshex
Ok, I'll stick with 2.0.4 for now then, until 2.1.4 comes out, then I'll give it another run. On Tuesday, October 6, 2015 at 12:22:14 PM UTC+1, Enrico Risa wrote: > > > It is not really a new implementation it is a bug fix that prevented you > from use lucene operator along > with other conditio

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread Enrico Risa
It is not really a new implementation it is a bug fix that prevented you from use lucene operator along with other conditions. Also spatial filter + full text did not worked. So we implemented an in memory check with lucene code in case the index is not used. I think this week will be released 2

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread Rui Pereira
Ok, when should I expect that to be released? I was upgrading from 2.0.4 . When was this new memory index implementation introduced? Thanks for your help On 6 October 2015 at 12:03, Enrico Risa wrote: > Hi syshex > > Yes it is a 2.1.3 issue > i've raised an issue. > https://github.com/oriente

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread Enrico Risa
Hi syshex Yes it is a 2.1.3 issue i've raised an issue. https://github.com/orientechnologies/orientdb-lucene/issues/73 I will fix it for the next hotfix 2.1.4 2015-10-06 12:03 GMT+02:00 syshex : > On 2.0.4 this query returns the expected results : > > SELECT * FROM Cpv WHERE [description] LUC

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread syshex
On 2.0.4 this query returns the expected results : SELECT * FROM Cpv WHERE [description] LUCENE "limpeza" On Tuesday, October 6, 2015 at 10:57:51 AM UTC+1, Enrico Risa wrote: > > Maybe there is some issue with inheritance. > > I'm checking > > 2015-10-06 11:46 GMT+02:00 Rui Pereira >: > >> Hey

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread Enrico Risa
Maybe there is some issue with inheritance. I'm checking 2015-10-06 11:46 GMT+02:00 Rui Pereira : > Hey , > > Supertable is actually Cpv (same class, I was renaming my outputs). > > So Cpv (or Supertable) has 4 subclasses , call them Cpv1, Cpv2, Cpv3, Cpv4 > . They all extend from Cpv. > >

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread Rui Pereira
Hey , Supertable is actually Cpv (same class, I was renaming my outputs). So Cpv (or Supertable) has 4 subclasses , call them Cpv1, Cpv2, Cpv3, Cpv4 . They all extend from Cpv. All data created is of type Cpv1,2,3,4 . The lucene index is created on Cpv in order to find all Cpvs that match

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread Enrico Risa
Can you post the schema also? Did Supertable extends other classes? Di you have also a class Cpv? 2015-10-06 10:42 GMT+02:00 syshex : > Hi Enrico > > Raw from studio for the explain query you requested: > > { > "result": [ > { > "@type": "d", > "@versio

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-06 Thread syshex
Hi Enrico Raw from studio for the explain query you requested: { "result": [ { "@type": "d", "@version": 0, "limit": -1, "luceneIndex": true, "fullySortedByIndex": false, "Cpv_description_totalHits": 30,

Re: [orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-05 Thread Enrico Risa
Hi syshex can you paste here the result of explain SELECT * FROM Supertable WHERE description LUCENE "limpeza*" 2015-10-05 20:07 GMT+02:00 syshex : > Hi everyone. > > I've got a table named Supertable with a String field called description. > > Created a Lucene index on it, like so : > > create

[orientdb] Issue with FULLTEXT using Lucene on 12.1.3

2015-10-05 Thread syshex
Hi everyone. I've got a table named Supertable with a String field called description. Created a Lucene index on it, like so : create index Supertable.description on Supertable (description) FULLTEXT ENGINE LUCENE return from studio was that the index was created, with 1150 indexed. If I qu