I would imagine that a major bug with FULLTEXT LUCENE INDEX would be a blocking bug. The Issue 5184 <https://github.com/orientechnologies/orientdb/issues/5184> bug makes any lucene index with more than one field useless. Did this just slip through the cracks or are people not really using lucene index much?
On Thursday, October 29, 2015 at 7:33:09 PM UTC-7, l.garulli wrote: > > Hi guys, > > We just released OrientDB v2.1.5. Please upgrade your production > environment with 2.1.x. > > For more information about the release: > https://github.com/orientechnologies/orientdb/releases/tag/2.1.5. > > To download it: http://orientdb.com/download/ > > Best Regards, > > Luca Garulli > Founder & CEO > OrientDB <http://orientdb.com/> > > -- --- 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.
