Re: Dismax + Dynamic fields

On Mon, 16 Jun 2008 14:22:12 -0400 "Yonik Seeley" <[EMAIL PROTECTED]> wrote: > There are two levels of dynamic field support. > > Specific dynamic fields can be queried with dismax, but you can't > wildcard the "qf" or other field parameters. Thanks Yonik. ok, that matches what I've seen - if i

easiest roadmap for server deployment

Hello All, It looks like all my tests with solr have been very conclusive: it's the way to go. Sadly enough, me nor our sysadmin have any experience with setting up tomcat, jetty, orion, . We have plenty of experience with other servers like lighttpd and apache, but that doesn't particularly help

Talk on Solr - Oakland, CA June 18, 2008

Hi - I'll be giving a talk on Solr at the East Bay Innovations Group (eBig) Java SIG on Wed, June 18. http://www.ebig.org/index.cfm?fuseaction=Calendar.eventDetail&eventID=16 This is an introductory / overview talk intended to get you from "What is Solr & Why Would I Use It" to "Cool, now I kno

RE: multicore vs. multiple instances

I think I'm about going the same way too. The thing is, we have few 100.000 users who are allowed to upload data which will be indexed. We're thinking of partitioning/sharding the index by user(groups). In the beginning, I see no need for one server per shard. So we'll probably put a certain ammou

Updating index

Hi! Updating index with post.jar just replaces the index with the defined xml's. But if there are, for example, two fields in all xml's that were changed, is there a way to update only these fields (incremental update)? If there are a lot of large xml's, it would be performance slowdown each time

Re: Dismax + Dynamic fields

On Tue, Jun 17, 2008 at 3:36 AM, Norberto Meijome <[EMAIL PROTECTED]> wrote: > On Mon, 16 Jun 2008 14:22:12 -0400 > "Yonik Seeley" <[EMAIL PROTECTED]> wrote: > >> There are two levels of dynamic field support. >> >> Specific dynamic fields can be queried with dismax, but you can't >> wildcard the "

Re: Dismax + Dynamic fields

Norberto Meijome wrote: > Thanks Yonik. ok, that matches what I've seen - if i know the actual > name of the field I'm after, I can use it in a query it, but i can't > use the dynamic_field_name_* (with wildcard) in the config. > > Is adding support for this something that is desirable / needed >

Re: Updating index

Mihails, Update is done as delete + re-add. You may also want to look at SOLR-139 in Solr JIRA. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: Mihails Agafonovs <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Tuesday, June

Re: Dismax + Dynamic fields

: > Is adding support for this something that is desirable / needed : > (doable??) , and is it being worked on ? : : You can use a wildcard with copyFrom to copy the dynamic fields that : match the pattern to another field that you can then query on. It seems : like that would cover your needs, no

Re: Re[2]: How to limit number of pages per domain

That looks like the correct way to apply the patch. I tried it and it worked for me. Otis P.S. no need to use reply-all, I'm subscribed to solr-user :) -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: JLIST <[EMAIL PROTECTED]> > To: Otis Gospodne

RE: Search query optimization

Hi, Thanks for your reply. I did some test on my test machine. http://stage.boomi.com:8080/solr/select/?q=account:1&rows=1000. It will return resultset 384 in 3ms. If I add a new AND condition as below: http://stage.boomi.com:8080/solr/select/?q=account:1+AND+recordeddate_dt :[NOW/DAYS-7DAYS+TO+

Re[4]: How to limit number of pages per domain

Hmm... I tried it with a Windows native port of patch, cygwin patch and also on Linux and got the same error. Is this, by any chance, going to be in solr 1.3 soon? Thanks, Jack > That looks like the correct way to apply the patch. I tried it and it worked > for me. > Otis > - Original Me

Re: Search query optimization

Hi, Probably because the [NOW/DAYS-7DAYS+TO+NOW] part gets rewritten as lots of OR clauses. I think that you'll see that if you add &debugQuery=true to the URL. Make sure your recorded_date_dt is not too granular (e.g. if you don't need minutes, round the values to hours. If you don't need ho

RE: Search query optimization

Thanks for reply. Here is the debugQuery output: − account:1 AND recordeddate_dt:[NOW/DAYS-1DAYS TO NOW] − account:1 AND recordeddate_dt:[NOW/DAYS-1DAYS TO NOW] − +account:1 +recordeddate_dt:[2008-06-16T00:00:00.000Z TO 2008-06-17T17:07:57.420Z] − +account:1

Re: Faceting on date fields

: If I do a search that returns 1 result with a created date of : "1993-01-01T00:00:00.000Z", I get this: : : :... : 1 : 1 This is because the "range queries" used in date faceting are "inclusive" of both bounding dates ... this was the simplest solution that we came up with at the t

Re: Search query optimization

Hi, This is what I was talking about: recordeddate_dt:[2008-06-16T00:00:00.000Z TO 2008-06-17T17:07:57.420Z] Note that the granularity of this date field is down to milliseconds. You should change that to be more coarse if you don't need such precision (e.g. no milliseconds, no seconds, no mi

Re: Re[2]: "null" in admin page

: Steps as follow: : 1. I download the solr example app. : 2. Unpack it. : 3. cd : 4. java -jar start.jar : 5. Try do use one of the links in admin webapp : 6. Get core=null I don't understand what you mean by "Get core=null" ... i understand that on the stats.jsp page the word "null" appears in

Re: Search query optimization

: Probably because the [NOW/DAYS-7DAYS+TO+NOW] part gets rewritten as lots : of OR clauses. I think that you'll see that if you add &debugQuery=true : to the URL. Make sure your recorded_date_dt is not too granular (e.g. : if you don't need minutes, round the values to hours. If you don't nee

RE: Search query optimization

Hi Otis, Thanks for your advice. Do you mean when we add the date data we need carefully select the granularity of the date field to make sure it is more coarse? How can we do this? We just access solr via http URL not API. If you talk about the query syntax, we do have NOW/DAY as round to DAY

Re: get the fields of solr

: I'm able to get the fields specified in my schema with this query: : /solr/admin/luke?show=schema&numTerms=0 that's what the "show=schema" does .. if you want all the field names regardless of wether they were explicitly or dynamicly created you just leave that option off... http://l

RE: Search query optimization

Hi Chris, Thanks for your suggestions. I did try the [NOW/DAY-7DAYS TO NOW/DAY], but it is not better. And I tried [NOW/DAY-7DAYS TO NOW/DAY+1DAY], I got some exception as below: org.apache.solr.core.SolrException: Query parsing error: Cannot parse 'account:1 AND recordeddate_dt:[NOW/DAYS-7DAYS

RE: Search query optimization

:Thanks for your suggestions. I did try the [NOW/DAY-7DAYS TO : NOW/DAY], but it is not better. And I tried [NOW/DAY-7DAYS TO : NOW/DAY+1DAY], I got some exception as below: : org.apache.solr.core.SolrException: Query parsing error: Cannot parse : 'account:1 AND recordeddate_dt:[NOW/DAYS-7DAYS

Re: easiest roadmap for server deployment

On 17-Jun-08, at 12:55 AM, Bram de Jong wrote: It looks like all my tests with solr have been very conclusive: it's the way to go. Glad to hear it! Sadly enough, me nor our sysadmin have any experience with setting up tomcat, jetty, orion, . We have plenty of experience with other servers

RE: Search query optimization

Hi Chris, Thank you very much for the detail suggestions. I just did the cache test. If most of requests return the same set of data, cache will improve the query performance. But in our usage, almost all requests have different data set to return. The cache hit ratio is very low. That's the reas

Re: easiest roadmap for server deployment

: Sadly enough, me nor our sysadmin have any experience with setting up : tomcat, jetty, orion, . : We have plenty of experience with other servers like lighttpd and apache, : but that doesn't particularly help. if you already use a package management system for your servers (RPM, deb, ports, et

RE: scaling / sharding questions

I cannot facet on one huge index; it runs out of ram when it attempts to allocate a giant array. If I store several shards in one JVM, there is no problem. Are there any performance benefits to a large index v.s. several small indexes? Lance -Original Message- From: Marcus Herou [mailto

RE: Search query optimization

: test. If most of requests return the same set of data, cache will : improve the query performance. But in our usage, almost all requests : have different data set to return. The cache hit ratio is very low. that's hwy i suggested moving clauses that are likely to be common (ie: your "within the

Hadoop get together @ Berlin

Hello, I am happy to announce the first German Hadoop Meetup in Berlin. We will meet at 5 p.m. MESZ next Tuesday (24th of June) at the newthinking store in Berlin Mitte: newthinking store GmbH Tucholskystr. 48 10117 Berlin Please see also: http://upcoming.yahoo.com/event/807782/ A big Thanks

"Did you mean" functionality

Hello everybody, I need to integrate the Lucene SpellChecker Contrib lib in my applycation, but I`m using the EmbeededSolrServer to access all indexes. I want to know what should I do (if someone have any step-by-step, link, tutorial or smoke signal) of what I need to do during indexing, and of

Re: How does solr.StrField handle punctuation?

: However, the following query produces no hits, even though I know from the : facets info that there are over 4000 matches in the index: : : fl=*,score&start=0&q=division_t:"Accounting"&company_facet:"Deloitte+%26+Touche"&qt=standard&wt=ruby&rows=30 That's not a "legal" URL ... note the "...&c

Re: "Did you mean" functionality

Hi Lucas, Have a look at (the patch in) SOLR-572, lots of work happening there as we speak. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: Lucas F. A. Teixeira <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Tuesday, June 17,

Re: "Did you mean" functionality

Hello Otis! Thanks a lot! []s, Lucas Lucas Frare A. Teixeira [EMAIL PROTECTED] Tel: +55 11 3660.1622 - R3018 Otis Gospodnetic escreveu: Hi Lucas, Have a look at (the patch in) SOLR-572, lots of work happening there as we speak. Otis -- Sematext -- http://sem

Re: Analyser doubt in solr

I'm not really sure that i understand your question at all ... it seems like maybe you are asking about natural language type problems (ie: question answering) but i'm not really sure. there are "question answering" type features provided by Solr, but off the top of my head you might have som

Re: How does solr.StrField handle punctuation?

Thanks for the reply. I was in a hurry and made the URL up to illustrate my point. The real query string is more like what you suggest. In any case I'm certain that the actual query being used is valid (Solr would complain if it weren't) and that the ampersand is somehow affecting results. Is ther

Re: How does solr.StrField handle punctuation?

: Thanks for the reply. I was in a hurry and made the URL up to illustrate my : point. The real query string is more like what you suggest. In any case I'm : certain that the actual query being used is valid (Solr would complain if it : weren't) and that the ampersand is somehow affecting results.

Re: Dismax + Dynamic fields

On Tue, 17 Jun 2008 09:43:58 -0400 Daniel Papasian <[EMAIL PROTECTED]> wrote: > Norberto Meijome wrote: > > Thanks Yonik. ok, that matches what I've seen - if i know the actual > > name of the field I'm after, I can use it in a query it, but i can't > > use the dynamic_field_name_* (with wildcard)

Re: Dismax + Dynamic fields

On Tue, 17 Jun 2008 08:16:41 -0700 (PDT) Chris Hostetter <[EMAIL PROTECTED]> wrote: > bingo. even if a wildcard like syntax was allowed in the qf/pf of dismax > since the same boost would be applied to each field the results would be > roughly the same as if you used copyField -- and searching

Re: "Did you mean" functionality

Also see http://wiki.apache.org/solr/SpellCheckComponent I expect to commit fairly soon. On Jun 17, 2008, at 5:46 PM, Otis Gospodnetic wrote: Hi Lucas, Have a look at (the patch in) SOLR-572, lots of work happening there as we speak. Otis -- Sematext -- http://sematext.com/ -- Lucene - So

Re: How does solr.StrField handle punctuation?

Here are the exact query strings I'm using. The only modification I made is to change the output formatter from Ruby to XML and run the output through a pretty printer. This is the one that returns the facet.fields I'm interested in. The problem field is the first one returned: Query: /solr/sele

Re: How does solr.StrField handle punctuation?

: 4114 : 1379 A-Ha! ... this is where the details relaly matter. unless your email program did something funky with the XML you sent, what this tells me is that you don't actually have the values "Deloitte & Touche" or "Ernst & Young" in your in

Re: How does solr.StrField handle punctuation?

Nailed it right on the head. That solves it. Thanks much! Jonathan hossman wrote: > > > : 4114 > : 1379 > > A-Ha! ... this is where the details relaly matter. unless your email > program did something funky with the XML you sent, what this te