Dennis Gearon 2010-10-10, 14:55
Erick Erickson 2010-10-10, 15:11
Dennis Gearon 2010-10-11, 00:47
Otis Gospodnetic 2010-10-11, 03:47
-Re: Records from DIH not easily queried for
Dennis Gearon 2010-10-11, 04:28
I am talking about the query for the DIH (Data Import Handler?) that queries the database to find records/documents to index. We originally were trying to import aout 20 fields, but have whittled down the schema file (my bad calling in config) to only try a few fields.
I myself have been STUDYING this whole Solr/Lucene product, while actually DOING the backend and interface to the front end. HE is doing the search engine and I'm trying to apply my limited knowledge and ask questions here.
I should have a pow wow with him so we present a united front to ask questions. I'll start a new thread when we do that. Thanks for the help, Otis. :-)
And for Solr/Lucene.
It is always a good idea to learn from your own mistakes. It is usually a better idea to learn from others’ mistakes, so you do not have to make them yourself. from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036'
EARTH has a Right To Life,
otherwise we all die.
--- On Sun, 10/10/10, Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
> From: Otis Gospodnetic <[EMAIL PROTECTED]>
> Subject: Re: Records from DIH not easily queried for
> To: [EMAIL PROTECTED]
> Date: Sunday, October 10, 2010, 8:47 PM
> The unique field does not have to be named "id".
> Fields are specified in schema.xml. There is no
> config.xml, although there is
> If a query is returning fields that you do not have defined
> in schema.xml, it's
> time to stop working on weekends! ;) Seriously,
> though, that cannot be
> happening. Maybe you can show the relevant part of
> your schema file, your
> response, and your request?
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
> ----- Original Message ----
> > From: Dennis Gearon <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Sent: Sun, October 10, 2010 8:47:29 PM
> > Subject: Re: Records from DIH not easily queried for
> > Thanks for answering on a Sunday :-)
> > What happens if the query returns extra fields
> that are not specified in the
> > And does the unque field have to be named 'id'?
> > Dennis Gearon
> > Signature Warning
> > ----------------
> > It is always a good idea to learn from your own
> mistakes. It is usually a
> >better idea to learn from others’ mistakes, so you
> do not have to make them
> >yourself. from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036'
> > EARTH has a Right To Life,
> > otherwise we all die.
> > --- On Sun, 10/10/10, Erick Erickson <[EMAIL PROTECTED]>
> > > From: Erick Erickson <[EMAIL PROTECTED]>
> > > Subject: Re: Records from DIH not easily
> queried for
> > > To: [EMAIL PROTECTED]
> > > Date: Sunday, October 10, 2010, 8:11 AM
> > > The phrase that jumps out is "with
> > > fields slightly modified". I'm
> > > guessing that your modifications are off by
> a little.
> > > Here's what
> > > I'd check first:
> > > 1> check the case. Sometimes the DB <->
> field link
> > > is case
> > > sensitive.
> > > 2> Look in your index via the admin page
> and look at
> > > your actual
> > > fields as reported there. Are they really
> what you expect?
> > > 3> Try your query with
> &debugQuery=on. Is what you
> > > get back
> > > what you expect?
> > > 4> Sometimes your browser cache will fool you,
> try the
> > > force-refresh
> > > combination on your browser.
> > >
> > > There's no magic here, nothing special or
> different about
> > > DIH
> > > imported data than any other sort. So it's
> > > certainly
> > > some innocent-seeming change that's not,
> typo, incorrect
> > > assumption, etc.
> > >
> > > If none of that works, you need to post your
> schema changes
> > > and
> > > your query results (with
> &debugQuery=on). Particularly,
Dennis Gearon 2010-10-11, 23:20