Yes, I thought that as well but I am seeing the same issues when I use an
index of type string or embeddedlist string
On Wednesday, April 22, 2015 at 5:55:27 AM UTC-4, Izzet Pembeci wrote:
>
> Personid has type long. So may be you can only create a Lucene index on a
> string property.
>
> iZzeT
>
> On Wednesday, April 22, 2015 at 12:20:05 AM UTC+3, sck2015 wrote:
>>
>> Hi all, has anyone seen this behavior before, I am creating a lucene
>> index and I don't see a match even though the index appears to have been
>> successfully created (I am using version 2.0.7)
>>
>>
>> orientdb {db=newSmallDB}> create index Personid on Person(personid)
>> FULLTEXT ENGINE LUCENE
>>
>>
>> Creating index...
>> Created index successfully with 1000 entries in 0.411000 sec(s).
>>
>>
>> Index created successfully
>> orientdb {db=newSmallDB}> select from index:Personid
>>
>>
>>
>> 0 item(s) found. Query executed in 0.0 sec(s).
>>
>>
>> OR, trying to select keys:
>>
>> orientdb {db=newSmallDB}> select key from index:Personid
>>
>>
>> 0 item(s) found. Query executed in 0.0 sec(s).
>>
>> Does anyone know why this may be happening? Ty, Sonu (same is whether
>> underlying type is string, embeddedlist string, long)
>>
>
--
---
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.
