Hi, You are obviously right in regards to keeping it updated, it's problematic.
If I'm understanding you correctly then there is no difference between the two. Both can be used to select interconnected parts of the graph for it to be indexed together. The main thing here is to be able to create a singe fulltext entry (document) from things stored separetly in the graph so that they can be search as a whole solely using the Lucene Query Parser. I do realize that OSQL is the only way to to a proper search in the graph. This is to tackle the same fulltext capabilities of the document-store even for information is spread out over the graph. Using a OSQL query to generate that document would be completely acceptable. And please remember that the "document" being indexed does not need to be stored, only indexed. Regards, -Stefán On Monday, 26 May 2014 20:45:34 UTC, Riccardo Tasso wrote: > > > 2014-05-26 11:05 GMT+02:00 <[email protected] <javascript:>>: > >> The only alternative that has come to mind is to create this "searchable >> document" that contains information from various vertices. > > > I think that creating a virtual document would bring the problem of > keeping it updated, if it is materialized. If it isn't materialized, which > is the difference between a virtual document and a query? > > Cheers, > Riccardo > -- --- 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.
