HI Lance,
I think you are discussing a different issue here. We are talking about
each row from each table represents a document in index. You look to discuss
about some documents may have multi-value fields which are stored in a
separate table in RDBMS because of normalization.
On Mon, Nov 9
There is a more fundamental problem here: Solr/Lucene index only
implements one table. If you have data from multiple tables in a
normalized index, you have denormalize the multi-table DB schema to
make a single-table Solr/Lucene index.
Your indexing will probably be faster if you a join in SQL to
On Sun, Nov 8, 2009 at 8:25 AM, Bertie Shen wrote:
> I have figured out a way to solve this problem: just specify a
> single blah blah blah . Under , specify
> multiple top level entity entries, each of which corresponds to one table
> data.
>
> So each top level entry will map one row in it to a
I have figured out a way to solve this problem: just specify a
single blah blah blah . Under , specify
multiple top level entity entries, each of which corresponds to one table
data.
So each top level entry will map one row in it to a document in Lucene
index. in DIH is *NOT* mapped to a documen
I have the same problem. I had thought we could specify multiple
blah blah blahs, each of which is mapping one table in the RDBMS.
But I found it was not the case. It only picks the first blah blah
blah to do indexing.
I think Rupert's and my request are pretty common. Basically there are
multip
You can only have one document tag and the entities must be nested
within that.
>From the wiki, if you issue a simple "/dataimport?command=full-import"
all top level entities will be processed.
>Maybe I should be more clear: I have multiple tables in my DB that I
>need to save to my Solr index.
DIH allows only tag. you may have multiple root
tags and you may invoke them by name(s). When no name is passed all
root entities are invoked one after another.
On Wed, Sep 9, 2009 at 5:12 AM, Rupert Fiasco wrote:
> Maybe I should be more clear: I have multiple tables in my DB that I
> need to s
Maybe I should be more clear: I have multiple tables in my DB that I
need to save to my Solr index. In my app code I have logic to persist
each table, which maps to an application model to Solr. This is fine.
I am just trying to speed up indexing time by using DIH instead of
going through my applic
