Re: Problem using db-data-config.xml

On Thu, Jun 11, 2009 at 2:41 AM, jayakeerthi s wrote: > As displayed above > *3739* > * * *4135* > * * *1402* > > are differing The request to the datasource is increasing ..and the > documents processed is less than the rows fetchedPlease advise If I am > missing something her

Re: Customizing results

Hi Michael, What is GNU gettext and how this can be used in a multilanguage scenario? Regards Revas On Wed, Jun 10, 2009 at 8:10 PM, Michael Ludwig wrote: > Manepalli, Kalyan schrieb: > >> Hi, >> I am trying to customize the response that I receive from Solr. In the >> index I have multiple fie

Re: How to use Lucene Query Syntax in Solr

On Thu, Jun 11, 2009 at 12:31 AM, chem leakhina wrote: > Could you please tell me about how to use Lucene Query Syntax in Solr? > My query example is that, I want to use wild card (*) with phrase. Solr supports the full Lucene QueryParser syntax, but wildcards in phrase queries isn't supported in

How to use Lucene Query Syntax in Solr

Hi Could you please tell me about how to use Lucene Query Syntax in Solr? My query example is that, I want to use wild card (*) with phrase. For example: I have field *text* and I want to search like *text:"Cam* Yel*"* to match with Cambodia Yellow or like *text:"Cambodia yel*"* Please help to

dismax parsing applied to specific fields

Hi I was wondering if there is a way of applying dismax parsing to specific fields, where there are multiple fields being searched - all with different query values e.g. author:(tolkien) AND title:(the lord of the rings) would be something like: dismax(author, tolkien) AND dismax(title, the lord

Re: Faceting on text fields

I'd call it related (their application in search encourages exploration), but also distinct enough to never mix them up. I think your assessment below is correct, although I'm not familiar with the details of Carrot2 any more (was once), so I can't tell you exactly which algo is used under the

does solr support summary

if user use keyword to search and get summary(auto generated by keyword)...like this doc filed: id, text id: 001 text: > Open source is a development method for software that harnesses the power > of distributed peer review and transparency of process. The promise of open > source is better qual

Re: Problem using db-data-config.xml

Many Thanks Noble the issue was with case of the field names. After fixing that I am getting the response for the full-data import cmd as *-* *-* * * * C:\apache-solr-nightly\example

Re: SortedIntDocSet vs HashDocSet

On Wed, Jun 10, 2009 at 3:52 AM, Marc Sturlese wrote: > I use to have a HashDocSet in my own Solr SearchComponent. As HashDocSet is > not used anymore in recent nightlies could I replace it for a > SortedIntDocSet (it didn't exist yet when I create my search component). > Does it make sense? Yep.

Build Failed

When running "ant example" to do an example configuration, I get the following message: BUILD FAILED /home/stagger2/Solr/apache-solr-1.3.0/common-build.xml:287: The following error occurred while executing this line: /home/stagger2/Solr/apache-solr-1.3.0/common-build.xml:209: The following error

Re: copyfield and 'store' and highlighting

ashokc schrieb: Do I have to declare 'field1' also to be stored? 'field1' is never returned in the response. I find the following Wiki page helpful when dealing with @stored, @indexed and friends: http://wiki.apache.org/solr/FieldOptionsByUseCase Michael Ludwig

Re: copyfield and 'store' and highlighting

ashokc wrote: Hi, I copy 'field1' to 'field2' so that I can apply a different set of analyzers & filters. Content wise, they are identical. 'field2' has to be stored because it is used for high-lighting. Do I have to declare 'field1' also to be stored? 'field1' is never returned in the response.

copyfield and 'store' and highlighting

Hi, I copy 'field1' to 'field2' so that I can apply a different set of analyzers & filters. Content wise, they are identical. 'field2' has to be stored because it is used for high-lighting. Do I have to declare 'field1' also to be stored? 'field1' is never returned in the response. Thanks. - ashok

Re: Servlet filter for Solr

I've tried both "url-pattern" (/*) and servlet-name in the filter mapping , but none of it seem to intercept the call. If I put (/*) only up to /solr gets intercepted. Since, I'm using multicore - calls like /solr/core0 don't get intercepted. I want both select and update to be monitored. Any ideas

Re: Solr relevancy score - conversion

Vijay_here schrieb: Would need an more proportionate score like rounded to 100% (95% relevant, 80 % relevant and so on). Is there a way to make solr returns such scores of such relevance. In XSLT: The "div" is the XPath division operator. Should be a straightforward mapping to any ot

Re: Faceting on text fields

Thanks for insight Otis. I have no awareness of ClusteringComponent until now. It is time to move to Solr 1.4 -Yao Otis Gospodnetic wrote: > > > Yao, > > Solr can already cluster top N hits using Carrot2: > http://wiki.apache.org/solr/ClusteringComponent > > I've also done ugly "manual count

Re: How to disable posting updates from a remote server

ashokc schrieb: I find that I am freely able to post to my production SOLR server, from any other host that can run the post command. So somebody can wipe out the whole index by posting a delete query. Control this at the IP level, have your server listen on 127.0.0.1 or on a private subnet add

Re: Customizing results

Manepalli, Kalyan schrieb: Hi, I am trying to customize the response that I receive from Solr. In the index I have multiple fields that contain the same data in different language. At the query time client specifies the language. Based on this param, I want to return the value, copied into a diff

Re: How to search date

Assuming the date is 2009-01-01 00:00:00 UTC... Before: my_date:[* TO 2009-01-01T00:00:00Z] After: my_date:[2009-01-01T00:00:00Z TO *] Between: my_date:[2009-01-01T00:00:00Z TO 2010-01-01T00:00:00Z] All: my_date:[* TO *] (or just don't put a date at all) Mat On Wed, Jun 10, 2009 at 02:27, chem l

Re: Faceting on text fields

Otis Gospodnetic schrieb: Solr can already cluster top N hits using Carrot2: http://wiki.apache.org/solr/ClusteringComponent Would it be fair to say that clustering as detailed on the page you're referring to is a kind of dynamic faceting? The faceting not being done based on distinct values o

Re: user feedback in solr

You can look at the HTTP server logs output by Jetty (or whatever server you have) that provides a lot of visibility into what people are looking for. However, there isn't that I know of a "ready to roll" analytics package for Solr It would be cool though! Eric On Jun 10, 2009, at

user feedback in solr

Hi all, I wanted to know if there is any provision to accommodate user feedback in the form of query logs and click logs, to improve the search relevance and ranking. Also, is there a possibility of it being included in the next version ? Thank you, Regards, Pooja

Re: Faceting on text fields

Yonik Seeley schrieb: Yep, all that sounds right. An additional optimization counts terms for the documents *not* in the set when the base set is over half the size of the index. Cool :-) Thanks for confirming my assumptions! Michael Ludwig

Re: fq vs. q

Fergus McMenemie schrieb: On Tue, Jun 9, 2009 at 7:25 PM, Michael Ludwig wrote: A filter query is cached, which means that it is the more useful the more often it is repeated. We know how often certain queries arise, or at least have the means to collect that data - so we know what might be c

SortedIntDocSet vs HashDocSet

I use to have a HashDocSet in my own Solr SearchComponent. As HashDocSet is not used anymore in recent nightlies could I replace it for a SortedIntDocSet (it didn't exist yet when I create my search component). Does it make sense? And another thing... Is there anyway to get a set of internal docu

Re: fq vs. q

>On Tue, Jun 9, 2009 at 7:25 PM, Michael Ludwig wrote: >> >> A filter query is cached, which means that it is the more useful the >> more often it is repeated. We know how often certain queries arise, or >> at least have the means to collect that data - so we know what might be >> candidates for