Filtered docs and positions enum

First sorry for the post to here and the solr list, not sure where this is most appropriately asked but since there is no response there I figured I'd try here... I have what I believe to be a fairly unique use case (as i have not seen it mentioned before) that I'm looking for some thoughts on. I

Re: Limiting the fields a user can query on

I would be fine with throwing a parse exception or excluding the particular clause. I will look at the StandardQueryNodeProcessorPipeline as well as Hoss' suggestion. Thank you very much! On Thu, Feb 20, 2014 at 4:20 AM, Trejkaz wrote: > On Thu, Feb 20, 2014 at 1:43 PM, Jamie Johnso

Limiting the fields a user can query on

Is there a way to limit the fields a user can query by when using the standard query parser or a way to get all fields/terms that make up a query without writing custom code for each query subclass?

Re: Store a query in a database for later use

I think you want to have a look at the QueryParser classes. Not sure which you're using to start with but probably the default QueryParser should suffice. On Thu, May 17, 2012 at 3:53 PM, Stefan Undorf wrote: > Hi, > > I want to store a query for later use in a database, like: > > 1. queryToPers

Re: query for documents WITHOUT a field?

Another possible solution is while indexing insert a custom token which is impossible to show up in the index otherwise, then do the filter based on that token. On Thu, Feb 16, 2012 at 4:41 PM, Uwe Schindler wrote: > As the documentation states: > Lucene is an inverted index that does not have p

Re: Lucene 4.0 Index Format Finalization Timetable

s we need to stick w/3.x for now.  You might be in a > different situation if you really need the 4.0 changes.  Maybe you can just > stick w/the current trunk and take responsibility for patching critical > bugfixes, hoping you won't have to recreate your index too many times... > &g

Re: Lucene 4.0 Index Format Finalization Timetable

p://8ball.tridelphia.net/ > > > On 12/06/2011 08:46 PM, Jamie Johnson wrote: >> >> Thanks Robert.  Is there a timetable for that?  I'm trying to gauge >> whether it is appropriate to push for my organization to move to the >> current lucene 4.0 implementation

Re: Lucene 4.0 Index Format Finalization Timetable

rently on trunk. I'm not looking for anything hard, just trying to plan as much as possible understanding that this is one of the implications of using trunk. On Tue, Dec 6, 2011 at 6:48 PM, Robert Muir wrote: > On Tue, Dec 6, 2011 at 6:41 PM, Jamie Johnson wrote: >> Is there a time

Lucene 4.0 Index Format Finalization Timetable

Is there a timetable for when it is expected to be finalized? I'm not looking for an exact date, just an approximate like (next month, 2 months 6 months,etc) - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For a

LocalLucene/Lucene Spatial

I am working on a project that is already using Lucene (through Hibernate Search) to perform full text queries and have since come across several sites with information about LocalLucene/Lucene Spatial. I was wondering if there was a timeline for having this work implemented that anyone was aware