Hi Enrico, Would it be possible for me to use the Lucene integration build my own flavor/version of the "document being indexed"?
I'm not sure if this request will make sense to you but I would like more control over what gets put into the indexed-document to allow for search based on the MultiFieldQueryParser on fields that are not directly stored on the Vertex such as embedded lists, embedded maps or even on edges or related vertices. Does that sound reasonable? Regards, -Stefán On Tuesday, 20 May 2014 19:46:49 UTC, ste...@activitystream.com wrote: > > Hi Enrico, > > Thank you. > > I have not been indexing Embedded maps so far but I would like to do that > now with the fulltext option. > > Regards, > - Stefán > > > On Tuesday, 20 May 2014 18:02:42 UTC, Enrico Risa wrote: >> >> Hi Stefan >> >> for multiple fields you could create it like a normal composite index >> >> create index V.name_song_type on V (name,song_type) FULLTEXT ENGINE LUCENE >> >> and then you can query it with >> >> select from V where [name,song_type] LUCENE "diddley" >> >> For fields with sub-properties how do you index them now? >> >> >> >> 2014-05-20 19:54 GMT+02:00 <ste...@activitystream.com>: >> >>> Hi, >>> >>> Can someone please outline the best practices for creating a full text >>> search index on multiple fields and fields with sub-properties. >>> >>> Regards, >>> -Stefán >>> >>> -- >>> >>> --- >>> 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 orient-databa...@googlegroups.com. >>> 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
