(albums:query OR tracks:query) AND NOT(tracks:query -> albums:query)
Is this it? That last clause does sound like a join.
How do you shard? Is it possible to put all associated albums and
tracks in one shard? You can then do a join query against each shard
and merge the output yourself.
On Fri,
Thanks, but I don't want to exclude all tracks that are associated
with albums, I want to exclude tracks that are associated with albums
*which match the query* (tracks and their associated albums may have
different tags). I don't think your suggestion covers that.
On Fri, Apr 6, 2012 at 9:35 AM,
I'd consider a field like "associated_with_album", and a
field that identifies the kind of record this is "track or album".
Then you can form a query like -associated_with_album:true
(where '-' is the Lucene or NOT).
And then group by kind to get separate groups of albums and
tracks.
Hope this h
I admit I just glanced at your problem statement, but
three things come to mind...
1> have you looked at the "limited join" patch and would
that work?
2> try searching the list for "hierarchical", very similar
questions have been discussed before, although I
don't quite remember the answers
, 2011 8:55 AM
To: solr-user@lucene.apache.org
Subject: Re: Schema Design Question
Of your first two options, I'd go with a multi-valued field for each book (1).
But kenf_nc's suggestion is a good one too.
On Sun, May 15, 2011 at 3:54 AM, kenf_nc wrote:
> create a separate document
Of your first two options, I'd go with a multi-valued field for each book (1).
But kenf_nc's suggestion is a good one too.
On Sun, May 15, 2011 at 3:54 AM, kenf_nc wrote:
> create a separate document for each book-bookshelf combination.
> doc 1 = book 1,shelf 1
> doc 2 = book 1,shelf 3
> doc 3 =
create a separate document for each book-bookshelf combination.
doc 1 = book 1,shelf 1
doc 2 = book 1,shelf 3
doc 3 = book 2,shelf 1
etc.
then your queries are q=book_id to get all bookshelfs a given book is on
or q=shelf_id to get all books on a given bookshelf.
Biggest problem people face wit
ith a large number of values or should you pass a large number of values
in as a Boolean clause?
Zac
-Original Message-
From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
Sent: Friday, May 13, 2011 10:37 AM
To: solr-user@lucene.apache.org
Subject: Re: Schema Design Question
H
Hi Zac,
Solr 4.0 (trunk) has support for relationships/JOIN. Have a look:
http://search-lucene.com/?q=solr+join
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
> From: Zac Smith
> To: "solr-
