Hi, I have asked a similar question and pointed out the usability of full-text indexes via composite-documents (like what you seem to need).
I think this is not currently supported and due to the multi-source/composite nature of such an index I think it will not be supported. Please let me know if you find a good solution to this problem. Regards, -Stefan On Friday, 28 November 2014 10:17:38 UTC, Marcel Pitch wrote: > > Hello everyone, > > > First, here is the structure of our graph to store locations and labels in > different cultures: > > > > <https://lh4.googleusercontent.com/-yzbdazRBZnI/VHhLgdL6YKI/AAAAAAAAAA8/miV6pHl4btY/s1600/CustomIndex.jpg> > > > We would now create a composite full-text index with the following > properties: > > * [ CityLabel.label, AdminZone2Label.label, AdminZone1Label.label, > CountryLabel.label, Culture.code, City.@rid ]* > > Is it possible to create it using the LUCENE engine? > > Or do we have to create a custom index engine? > > > Thank you for your answers and have a nice day > -- --- 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.
