(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
Apologies if this is a very straightforward schema design problem that
should be fairly obvious, but I'm not seeing a good way to do it.
Let's say I have an index that wants to model Albums and Tracks, and
they all have arbitrary tags attached to them (represented by
multivalue string type fields).
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
Hi there
I have a question regarding how to setup schema for some data. This data is
basically parent-child data for different types of records .. so
a bunch of records representing projects and subprojects where each
subproject has a parent project .. and a project has many child sub projects
an
, 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
edly or RDBMs orientedly. You need to think differently.
> Solr/Lucene find text and they find it very fast over huge amounts of data.
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Schema-Design-Question-tp2939045p2942809.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
with Solr schema design is thinking either
object orientedly or RDBMs orientedly. You need to think differently.
Solr/Lucene find text and they find it very fast over huge amounts of data.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Schema-Design-Question-tp2939045p2942809
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
"solr-user@lucene.apache.org"
> Sent: Fri, May 13, 2011 12:28:35 PM
> Subject: Schema Design Question
>
> Let's say I have a data model that involves books and bookshelves. I have
> tens
>of thousands of books and thousands of bookshelves. There is a
Let's say I have a data model that involves books and bookshelves. I have tens
of thousands of books and thousands of bookshelves. There is a many-many
relationship between books & bookshelves. All of the books are indexed by SOLR.
I need to be able to query SOLR and get all the books for a give
I have documents that represent Companies. Each company has a field "Internet"
which is a boolean field, True means the company is an Internet company.
There's also another field "location" which is the city the company is located
in, eg. "Austin" or "Houston".
A company can be both an Internet
13 matches
Mail list logo
