I downloaded 2.1.0 tag from this repo:
https://github.com/orientechnologies/orientdb-lucene/releases/tag/2.1.0

and built it (but with key that skip tests: mvn assembly:assembly 
-DskipTests). Tests failed with exception - could not connect to 
127.0.0.1:2424/graph... , connection refused

Then I put orientdb-lucene-2.1.0-dist.jar into /plugins dir on server and 
tried again.
Result not changed - lucene indexes fully cleared after restart.

понедельник, 17 августа 2015 г., 13:35:01 UTC+3 пользователь Enrico Risa 
написал:
>
> Hi Albert
>
> this test has been running i think since 2.0.x, and also 2.1
> i will manually test it with your step.
>
> Thanks
>
> Enrico
>
> 2015-08-17 12:27 GMT+02:00 Albert Kovalchuk <[email protected] 
> <javascript:>>:
>
>> Hi Enrico, is this test from repository for orientdb 2.0...?
>>
>> From pom.xml in repo:
>> <orientdb.version>2.0-M3</orientdb.version>
>>
>> There is no problem in 2.0.9 (I didn't tried 2.0.10..., upgraded to 2.1), 
>> only in 2.1.0.
>>
>> I do this:
>>
>> 1) create classes
>> 2) create indexes
>> 3) write vertices
>> 4) in console connect and type "info", see number of records in indexes > 
>> 0
>> 5) exit from console, restart service: sudo service orientdb stop/start
>> 6) go to console, connect, type "info", see number of records in lucene 
>> fulltext indexes: all is 0
>> other indexes (usual unique/not_unique) remain consistent after restart.
>>
>>
>> понедельник, 17 августа 2015 г., 12:13:21 UTC+3 пользователь Enrico Risa 
>> написал:
>>>
>>> Hi Albert
>>>
>>> we have this test
>>>
>>>
>>> https://github.com/orientechnologies/orientdb-lucene/blob/master/src/test/java/com/orientechnologies/test/LuceneCreateIndexRemote.java
>>>
>>> that check index consistency at restart and it works
>>>
>>> How do you restart the ODB server?
>>>
>>> 2015-08-16 22:03 GMT+02:00 Albert Kovalchuk <[email protected]>:
>>>
>>>> Hi Enrico, there are no errors, only INFO & FINE entries. I tried with 
>>>> latest 2.1.0-SNAPSHOT with same result. Attachment - log.zip file.
>>>>
>>>> воскресенье, 16 августа 2015 г., 21:53:03 UTC+3 пользователь Enrico 
>>>> Risa написал:
>>>>>
>>>>> Hi Albert do you have some error in log file?
>>>>> Il 16/ago/2015 20:43, "Albert Kovalchuk" <[email protected]> ha 
>>>>> scritto:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> In 2.0.9 I have created database via Java script:
>>>>>>
>>>>>>         OrientVertexType file = graph.createVertexType("File");
>>>>>>         file.createProperty("name", OType.STRING);
>>>>>>         file.createProperty("description", OType.STRING);
>>>>>>         file.createProperty("tags", OType.EMBEDDEDLIST, OType.STRING);
>>>>>>         file.createProperty("keyWords", OType.EMBEDDEDLIST, 
>>>>>> OType.STRING);
>>>>>>         file.createProperty("size", OType.LONG);
>>>>>>         file.createProperty("path", OType.STRING);
>>>>>>
>>>>>>         file.createIndex("File.descriptionLFTS", "FULLTEXT", null, 
>>>>>> null, "LUCENE", new String[] {"description"});
>>>>>>         file.createIndex("File.tagsLFTS", "FULLTEXT", null, null, 
>>>>>> "LUCENE", new String[] {"tags"});
>>>>>>         file.createIndex("File.keyWordsLFTS", "FULLTEXT", null, null, 
>>>>>> "LUCENE", new String[] {"keyWords"});
>>>>>>
>>>>>> After upgrade to 2.1.0 I create schema, create data like
>>>>>>
>>>>>>         int countFile = 1000;
>>>>>>         for (int i = 1; i <= countFile; i++) {
>>>>>>             graph.addVertex("class:File", "name", "File " + i + 
>>>>>> ".pdf", "description", "Desc " + i, "tags", "Tags " + i, "keyWords", 
>>>>>> "KeyWords " + i, "size", i, "path", "/home/user/filestorage/file_" + i + 
>>>>>> ".pdf");
>>>>>>         }
>>>>>>
>>>>>> When I invoke console in 2.0.9, connect and type "info", I saw:
>>>>>>
>>>>>>  File.descriptionLFTS                       | FULLTEXT   | 
>>>>>> File                | descrip...     |       1000 |
>>>>>>  File.keyWordsLFTS                          | FULLTEXT   | 
>>>>>> File                | keyWords       |       1000 |
>>>>>>  File.tagsLFTS                              | FULLTEXT   | 
>>>>>> File                | tags           |       1000 |
>>>>>>
>>>>>> After orientdb service restart indexes was not lost.
>>>>>>
>>>>>> But after upgrade to 2.1.0, DB creating and restarting service, 
>>>>>> indexes cleared:
>>>>>>
>>>>>>  File.descriptionLFTS                       | FULLTEXT   | 
>>>>>> File                | descrip...     |          0 |
>>>>>>  File.keyWordsLFTS                          | FULLTEXT   | 
>>>>>> File                | keyWords       |          0 |
>>>>>>  File.tagsLFTS                              | FULLTEXT   | 
>>>>>> File                | tags           |          0 |
>>>>>>
>>>>>> I used index rebuild, but on new writes (even using graoh.commit()) 
>>>>>> indexes rolled back to old rebuild attempt after restart ((.
>>>>>>
>>>>>> How to fix it?
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>> -- 
>>>>>>
>>>>>> --- 
>>>>>> 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.
>>>>
>>>
>>> -- 
>>
>> --- 
>> 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] <javascript:>.
>> 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.

Reply via email to