Ah. That makes sense then. I wasn't sure if that was the best way to
go about things or not. I didn't want to end up with a bunch of
fields that were not being used all the time if it would cause a
degradation in search quality.
+--------------------------------------------------------+
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
+--------------------------------------------------------+
On Apr 19, 2007, at 12:59 PM, Erik Hatcher wrote:
Matthew,
All that is meant by "object_types" is an additional stored/indexed
field in the Solr schema that gets added to every document
providing context of which type it is (shoes or brands). Then you
can limit searches to a particular area by just filtering on
type:shoes, for example.
Erik
p.s. I could use some new shoes!
On Apr 19, 2007, at 3:17 PM, Matthew Runo wrote:
I'll actually be doing this in Perl..
any ideas on perl? heh
+--------------------------------------------------------+
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
+--------------------------------------------------------+
On Apr 19, 2007, at 11:59 AM, Cody Caughlan wrote:
If you're doing this in Ruby, there is an "acts_as_solr" plugin for
Rails which takes exactly this approach to store all different kinds
of Model objects in the same index...I just "took" the idea from
there...
/Cody
On 4/19/07, Matthew Runo <[EMAIL PROTECTED]> wrote:
Ah hah! This appears to be what I'm interested in doing.
I'll have to read up on object_types.
+--------------------------------------------------------+
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
+--------------------------------------------------------+
On Apr 19, 2007, at 10:04 AM, Cody Caughlan wrote:
> Why not just store an additional "object_type" field which
> differentiates between the actual type of data you are looking
for?
>
> So if you're looking for some shoes:
>
> (size:8 AND color:'blue') AND object_type:'shoe'
>
> Or if you're searching on brands
>
> (genre:'skater' AND brand_desc:'skater boy') AND
object_type:'brand'
>
> I apologize if I misunderstood your question.
>
> /cody
>
> On 4/19/07, Matthew Runo <[EMAIL PROTECTED]> wrote:
>> Hey there-
>>
>> I was wondering if the following was possible, and, if so,
how to set
>> it up...
>>
>> I want to index two different types of data, and have them
searchable
>> from the same interface.
>>
>> For example, a group of products, with size, color, price,
etc info.
>> And a group of brands, with brand, genre, brand description,
etc info
>>
>> So, the info does overlap some. But a lot of the fields for each
>> "type" don't matter to the other. Is there a way to set up two
>> different schema so that both types may be indexed with relative
>> ease?
>>
>> +--------------------------------------------------------+
>> | Matthew Runo
>> | Zappos Development
>> | [EMAIL PROTECTED]
>> | 702-943-7833
>> +--------------------------------------------------------+
>>
>>
>>
>