Re: complex query is stumping me

Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/complex-query-is-stumping-me-tp4319237p4319271.html Sent from the Solr - User mailing list archive at Nabble.com.

complex query is stumping me

hi all. i'm attempting to grab up a swath of data based on some parameters that i'm finding difficult to express in a query: - i'd like to get all the data from a purchasing group (simple fq on their ids) - where items are grouped on one (or one of a few) unique identifiers (grouping?

Re: Solr: Elevate with complex query specifying field names

Hi Thomas, The query elevation component matches queries exactly with entries in elevate.xml. You can nominate a query field type that is used to process the query before matching, but that won't help you when your queries have explicit boosts. Are you using the eDismax query parser? If so, you c

Solr: Elevate with complex query specifying field names

I have Solr as the backend to an ECommerce solution where the fields can be configured to be searchable, which generates a schema.xml and loads it into Solr. Now we also allow to configure Solr search weight per field to affect queries, so my queries usually look something like this: spellch

Re: Complex query combining fq and q with join

ID fromIndex=document v='(DocNameS:" PeterRES")'} ) -- View this message in context: http://lucene.472066.n3.nabble.com/Complex-query-combining-fq-and-q-with-join-tp4091563p4091725.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Complex query, need filtering after query not before

: 700ms. The problem is, we are using geofiltering and that is happening * : before* the queries, so we have to geofilter on the 1B docs to restrict our : set of docs first, and then do the query on a name field. But it seems that ... : I've looked at the "cache=false" param, and the "co

Re: Is complex query like this possible?

Hello, Chris. Thank you and Mikhail for the explanation. I'll think about changing the model of indexing to be able to handle this case. > : DIR:true > : PATH:/root/folder1/folder2/ > : NAME:folder3 > : SIZE:0 > ... > : DIR:false > : PATH:/root/folder1/folder2/folder3/ > : NAME:image.jpg

Re[2]: Is complex query like this possible?

: DIR:true : PATH:/root/folder1/folder2/ : NAME:folder3 : SIZE:0 ... : DIR:false : PATH:/root/folder1/folder2/folder3/ : NAME:image.jpg : SIZE:1234567 ... : your solution). Also, in my previous example a file of specified type : may be deeper than one level: if there are /root/fol

Re: Re[2]: Is complex query like this possible?

t1.name LIKE '%test%' AND (SELECT > COUNT(*) FROM indexed_files t2 WHERE t2.path LIKE CONCAT(t1.path, '%') AND > t2.name LIKE '%jpg') > 0; > > > The question is: is it possible to do such search in Solr by single query? > Single query is imp

Re[2]: Is complex query like this possible?

quot; and "rows" parameters), so we should avoid filtering of wrong results in our code. I've read Solr wiki about nested queries but haven't found a way to do it. BTW, does Solr provide equivalent of "SELECT COUNT(*)" statement to access count of found records dir

Re: Is complex query like this possible?

h LIKE CONCAT(t1.path, '%') AND > t2.name LIKE '%jpg') > 0; > > The question is: is it possible to do such search in Solr by single query? > Single query is important because we need to use Solr's paging ("start" and > "rows" parameters), so

Is complex query like this possible?

, does Solr provide equivalent of "SELECT COUNT(*)" statement to access count of found records directly in Solr query? Or such complex query is completely impossible? -- Best regards, Asv mailto:asvs...@gmail.com

Re: Complex query, need filtering after query not before

Hello Jay, You can lose some precision in favour of performance: reducing precision of coordinates (by putting them onto grid) you can increase hit ratio; then try bbox for faster rough filtration http://wiki.apache.org/solr/SpatialSearch#bbox_-_Bounding-box_filter and apply geodist() function in

Complex query, need filtering after query not before

I have a project where we need to search 1B docs and still have results < 700ms. The problem is, we are using geofiltering and that is happening * before* the queries, so we have to geofilter on the 1B docs to restrict our set of docs first, and then do the query on a name field. But it seems that

Re: How can I check if a more complex query condition matched?

: I have a more complex query condition like this: : : (city:15 AND country:60)^4 OR city:15^2 OR country:60^2 : : What I want to achive with this query is basically if a document has : city = 15 AND country = 60 it is more important then another document : which only has city = 15 OR country

Re: How can I check if a more complex query condition matched?

> > Is there anything else I could try? > > On Tue, Dec 27, 2011 at 12:48 PM, Ahmet Arslan wrote: >>> I have a more complex query condition >>> like this: >>> >>> (city:15 AND country:60)^4 OR city:15^2 OR country:60^2 >>> >>> What I wa

Re: How can I check if a more complex query condition matched?

: >> I have a more complex query condition >> like this: >> >> (city:15 AND country:60)^4 OR city:15^2 OR country:60^2 >> >> What I want to achive with this query is basically if a >> document has >> city = 15 AND country = 60 it is more important then

Re: How can I check if a more complex query condition matched?

> I have a more complex query condition > like this: > > (city:15 AND country:60)^4 OR city:15^2 OR country:60^2 > > What I want to achive with this query is basically if a > document has > city = 15 AND country = 60 it is more important then > another document &g

How can I check if a more complex query condition matched?

I have a more complex query condition like this: (city:15 AND country:60)^4 OR city:15^2 OR country:60^2 What I want to achive with this query is basically if a document has city = 15 AND country = 60 it is more important then another document which only has city = 15 OR country = 60

Re: server down caused by complex query

Thanks Jason -- View this message in context: http://lucene.472066.n3.nabble.com/server-down-caused-by-complex-query-tp3535506p3581218.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: server down caused by complex query

: Because our user send very long and complex queries with asterisk and near : operator. : Sometimes near operator exceeds 1,000 and keywords almost include asterisk. : If such query is sent to server, jvm memory is full. (our jvm memory "near" operator isn't something I know of as a built in fea

server down caused by complex query

http://lucene.472066.n3.nabble.com/server-down-caused-by-complex-query-tp3535506p3535506.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: complex query

Thanks for your attention. I think I was just a little over-worried about search performance,. Fortunately, solr works pretty nice until present, it's fast enough for me. 2010/1/20 Chris Hostetter > > : I have considered building lucene index like: > : Document: { title, content, author, frien

Re: complex query

: I have considered building lucene index like: : Document: { title, content, author, friends } That seems like the right appraoch. : Thus, author and friends are two seperate fields. so I can boost them : seperately. : The problem is, if a document's author is the logged-in user, it's uncessar

Re: complex query

2010/1/12 Wangsheng Mei > I have considered building lucene index like: > Document: { title, content, author, friends } > Thus, author and friends are two seperate fields. so I can boost them > seperately. > The problem is, if a document's author is the logged-in user, it's > uncessary to search

Re: complex query

I have considered building lucene index like: Document: { title, content, author, friends } Thus, author and friends are two seperate fields. so I can boost them seperately. The problem is, if a document's author is the logged-in user, it's uncessary to search the friends field, because it would n

complex query

Hi, ALL! I have two tables in database. t_article { title, content, author } t_friend { person_A, person_B } note that in t_friend is many-to-many relation。 When a logged-in user, search articles with a query word, 3 factors should be considered in. factor 1. relevency score facto