Re: Is MemoryIndex and Spatial stuff combination supported?

2016-01-20 Thread david.w.smi...@gmail.com
Yup. Just to clarify for the O.P., after getting the SpatialStrategy instance, call createIndexableFields() which returns a list of Field instances, which you can then call tokenStream() on as Alan indicated. This should work fine for any of the SpatialStrategy instances. On Wed, Jan 20, 2016 at

Re: Is MemoryIndex and Spatial stuff combination supported?

2016-01-20 Thread Alan Woodward
Depending on the type of field, you can normally do: Field myField = … index.addField(fieldName, myField.tokenStream(null, null)) I agree that this could be a bit nicer, though. MemoryIndex doesn't support DocValues yet either, although I think there is an open ticket to add that. Alan Woodwar

Is MemoryIndex and Spatial stuff combination supported?

2016-01-20 Thread xavi jmlucjav
Hi, I am on lucene 5.3.1 I am running a doc at a time through a bunch of Queries. This is working nicely with the MemoryIndex and combinations of TermQuery/NumericRangeQuery. Now I wanted to add spatial stuff, so I happily added more queries with SpatialStrategy.makeQuery(...). But, when I go to

Re: Replacement for Filter-as-abstract-class in Lucene 5.4?

2016-01-20 Thread Adrien Grand
Uwe, maybe we could promote ConstantScoreWeight to an experimental API and document how to build simple queries based on it? Le ven. 15 janv. 2016 à 09:51, Christoph Kaser a écrit : > Nevermind, I missed the part about it being a base class for own queries. > > Sorry for the confusion! > > Am 15