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.

Reply via email to