Re: history
Accidentally I have a very similar use case. Thanks for advice. On 7/8/07, Yonik Seeley <[EMAIL PROTECTED]> wrote: On 7/7/07, Brian Whitman <[EMAIL PROTECTED]> wrote: > I have been trying to plan out a history function for Solr. When I > update a document with an existing unique key, I would like the older > version to stay around and get tagged with the date and some metadata > to indicate it's not "live." Any normal search would not touch > history documents. Interesting... One might be able to accomplish this with the update processors that Ryan & I have been batting around for the last few days, in conjunction with updateable documents, which is on-deck. The first idea that comes to mind is that during an update, you could change the id of the older document to be something like id_, and reindex it with the addition of a live:false field. For normal queries, use a filter of -live:false filter. For all old of a document, use a prefix query id:mydocid_* for all versions of a document, use query id:mydocid* So if you can hold off a little bit, you shouldn't need a custom query handler. This will be a good use case to ensure that our request processors and updateable documents are powerful enough. -Yonik -- Regards, Cuong Hoang
Solrsharp: direction
I've been asked a few questions of late that all have a familiar theme: what's going on with solrsharp development? Well, I've been working on the next iteration of the Solrsharp client library, attempting to bring it more in line with the capabilities of Solr, at least as of the 1.2 release. The goal of the Solrsharp project is to enable C# applications to take full advantage of Solr. Here's what happening: the main feature in development right now is the creation of RequestHandler objects. Solrsharp uses default handlers for queries and updates (/select and /update); the RequestHandler objects will enable assignable solr requesthandlers to any query. While assigning a request handler for a specific query is an active step, loading the solr-configured request handlers will be passive. The default handlers will still apply, in case you don't require any different handlers. If anyone has suggestions or comments around this, please pass them along. Ideally, we would begin thinking about Solr 1.3 features and how Solrsharp would be extended to utilize those as well. Any comments about future capabilities and what clients need to do to take advantage of those are welcome. cheers, jeff r.
partial word searches
Yo guys, quick question..I have a pretty simple solr instance running.. the relevant part of the schema is as such: I've got stuff indexed fine. Let's say I do a query as such: last-name:Anderson I get 27 records (the correct result), so far so good... now I want to provide a looser query: last-name:And* Now I get 0 results back.odd.. so I try wtithout regex: last-name:And 0 results back... I looked at the Lucene query syntax and from there it looks like it should just work but partial word matching doesn't seem to be working. Any clues? Thanks all -- alessandro ferrucci
Re: partial word searches
On 7/8/07, Alessandro Ferrucci <[EMAIL PROTECTED]> wrote: [...] last-name:And* Now I get 0 results back.odd.. Since "text" probably has a lowercase filter, try last-name:and* Wildcard queries aren't run through the query analyzer because things like stemming wouldn't work with partial words. -Yonik
