The issue's not about indexing, the issue's about storage.  It seems like
the fields (sections, colors, sizes) are all not being stored, even though
store=true.

I could not get Luke to work, no.  The webstart just hangs at downloading
0%.

Thanks,

John

On Mon, Mar 8, 2010 at 12:06 PM, Erick Erickson <erickerick...@gmail.com>wrote:

> Sorry, won't be able to really look till tonight. Did you try Luke? What
> did
> it
> show?
>
> One thing I did notice though...
>
> field name="sections" type="string" indexed="true" stored="true"
> multiValued="true"/>
>
> string types are not analyzed, so the entire input is indexed as
> a single token. You might want "text" here....
>
> Erick
>
> On Mon, Mar 8, 2010 at 11:37 AM, John Ament <my.repr...@gmail.com> wrote:
>
> > Erick,
> >
> > I'm sorry, but it's not helping much.  I don't see anything on the admin
> > screen that allows me to browse my index.  Even using Luke, my assumption
> > is
> > that it's not loading correctly in the index.  What parameters can I
> change
> > in the logs to make it print out more information? I want to see what the
> > query is returning I guess.
> >
> > Thanks,
> >
> > John
> >
> > On Mon, Mar 8, 2010 at 11:23 AM, Erick Erickson <erickerick...@gmail.com
> > >wrote:
> >
> > > Try http://<localhost address and port>/solr/admin. You'll see a bunch
> > > of links that'll allow you to examine many aspects of your
> installation.
> > >
> > > Additionally, get a copy of Luke (Google Lucene Luke) and point it at
> > > your index for a detailed look at the index.
> > >
> > > Finally, the SOLR log file might give you some clues...
> > >
> > > HTH
> > > Erick
> > >
> > > On Mon, Mar 8, 2010 at 10:49 AM, John Ament <my.repr...@gmail.com>
> > wrote:
> > >
> > > > Where would I see this? I do believe the fields are not ending up in
> > the
> > > > index.
> > > >
> > > > Thanks
> > > >
> > > > John
> > > >
> > > > On Mon, Mar 8, 2010 at 10:34 AM, Erick Erickson <
> > erickerick...@gmail.com
> > > > >wrote:
> > > >
> > > > > What does the solr admin page show you is actually in your index?
> > > > >
> > > > > Luke will also help.
> > > > >
> > > > > Erick
> > > > >
> > > > > On Mon, Mar 8, 2010 at 10:06 AM, John Ament <my.repr...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > All,
> > > > > >
> > > > > > So I think I have my first issue figured out, need to add terms
> to
> > > the
> > > > > > default search.  That's fine.
> > > > > >
> > > > > > New issue is that I'm trying to load child entities in with my
> > > entity.
> > > > > >
> > > > > > I added the appropriate fields to solrconfig.xml
> > > > > >
> > > > > >    <field name="sections" type="string" indexed="true"
> > stored="true"
> > > > > > multiValued="true"/>
> > > > > >    <field name="colors" type="string" indexed="true"
> stored="true"
> > > > > > multiValued="true"/>
> > > > > >    <field name="sizes" type="string" indexed="true" stored="true"
> > > > > > multiValued="true"/>
> > > > > >
> > > > > > And I updated my document to match
> > > > > >
> > > > > >    <document>
> > > > > >        <entity name="product" query="select product_id,
> product_id
> > as
> > > > > > id,vendor_label_name, sku2,
> > > > > style,product_name,delivery_time,regular_price,
> > > > > > copy_field,bullet1,bullet2,bullet3,bullet4,bullet5,bullet6,
> > > > > > bullet7,bullet8,bullet9,bullet10,bullet11,bullet12 from product_v
> > > where
> > > > > > status_code = 'ACTV' and regular_master_variant in (2,1)">
> > > > > >            <entity name="section_product" query="select
> > section_title
> > > > as
> > > > > > sections from section s, section_product sp where sp.section_id =
> > > > > > s.section_id and sp.product_id='${product.product_id}'"/>
> > > > > >            <entity name="color_product" query="select distinct
> > > > > > aev.enum_value as colors from product_attribute_enum
> > > > > > pae,attribute_enum_value aev, sub_product sp where pae.product_id
> =
> > > > > > sp.sub_product_id and pae.attribute_type_id =
> aev.attribute_type_id
> > > and
> > > > > > pae.attribute_value_id = aev.attribute_value_id and
> > > > pae.attribute_type_id
> > > > > =
> > > > > > 107 and sp.master_product_id = '${product.product_id}'"/>
> > > > > >            <entity name="size_product" query="select distinct
> > > > > > aev.enum_value as sizes from product_attribute_enum
> > > > > > pae,attribute_enum_value
> > > > > > aev, sub_product sp where pae.product_id = sp.sub_product_id and
> > > > > > pae.attribute_type_id = aev.attribute_type_id and
> > > > pae.attribute_value_id
> > > > > =
> > > > > > aev.attribute_value_id and pae.attribute_type_id = 108 and
> > > > > > sp.master_product_id = '${product.product_id}'"/>
> > > > > >        </entity>
> > > > > >    </document>
> > > > > >
> > > > > > So my expectation is that there will be 3 new fields associated
> > with
> > > it
> > > > > > that
> > > > > > are multivalued: sizes, colors, and sections.
> > > > > >
> > > > > > The full-import seems to work correctly.  I get the appropriate
> > > number
> > > > of
> > > > > > documents in my searches.  However, sizes, colors and sections
> all
> > > come
> > > > > up
> > > > > > null (well, I should say they don't come up when I search for
> > them).
> > > > > >
> > > > > > Any ideas on why it won't load these 3 child entities?
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > John
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to