Re: Structured Lucene documents

Hi All, The Structured (or Multi-Page, Multi-Part) document problem is a problem I've been thinking about for a while. A couple of years ago when the project I was working on was using Lucene only (no Solr), we solved this problem in several steps. At the point of ingestion we created a custom

Re: Will turning off the stored setting on a field remove it from the index?

On 12-Oct-07, at 4:39 PM, BrendanD wrote: We have some fields that we're currently storing in the index (for example product_name, short_description, etc). We'd like to stop storing them in the index as we're going to start faulting them in from the database instead so that the content is

Will turning off the stored setting on a field remove it from the index?

Hi, We have some fields that we're currently storing in the index (for example product_name, short_description, etc). We'd like to stop storing them in the index as we're going to start faulting them in from the database instead so that the content is fresh. If we change our config to stop stori

Re: dismax downweighting

would a dismax boost that's negative work? ie.. name^-1 and description^-1 ? ++ | Matthew Runo | Zappos Development | [EMAIL PROTECTED] | 702-943-7833 ++ On Oct 12, 2007, at

dismax downweighting

i have a dismax query where I want to boost appearance of the query terms in certain fields but "downboost" appearance in others. The practical use is a field containing a lot of descriptive text and then a product name field where products might be named after a descriptive word. Consider

Re: solr not finding all results

Sorry, I've figured out my own problem. There is a problem with the way I create the xml document for indexing that was causing some of the "comments" fields to not be listed correctly in the default search field, "content". On 10/12/07, Kevin Lewandowski <[EMAIL PROTECTED]> wrote: > I've found an

solr not finding all results

I've found an odd situation where solr is not returning all of the documents that I think it should. A search for "Geckoplp4-M" returns 3 documents but I know that there are at least 100 documents with that string. Here is an example query for that phrase and the result set: http://localhost:9020/

Solr, operating systems and globalization

We discovered and verified an issue in SolrSharp whereby indexing and searching can be disrupted without taking Windows globalization & culture settings into consideration. For example, European cultures affect numeric and date values differently from US/English cultures. The resolution for this

Re: Opensearch XSLT

There is a file ${SOLR_HOME}/conf/xslt/example_rss.xsl which is easily modified to transform Solr's output to OpenSearch. Works great, though fixing the date format is a hassle. The supported, searchable Solr date format is not the OpensSearch standard. On 10/12/07, Robert Young <[EMAIL PROTEC

Re: Opensearch XSLT

There is a request handler in 1.2 for Atom. That might be close. OpenSearch was a pretty poor design and is dead now, so I wouldn't expect any new implementations. Google's GData (based on Atom) reuses the few useful OpenSearch elements needed for things like number of hits. Solr's Atom support re

Opensearch XSLT

Hi, Does anyone know of an XSLT out there for transforming Solr's default output to Opensearch format? Our current frontend system uses opensearch so we would like to integrate it like this. Cheers Rob

Re: quickie: do facetfields use same cached items in field cache as FQ-param?

as a related question: is here a way to inspect the queries currently in the filtercache? Britske wrote: > > Yeah i meant filter-cache, thanks. > It seemed that the particular field (cityname) was using a > keywordtokenizer (which doens't show at the front) which is why i missed > it i guess :