> We are currently doing this via a JOIN on the numeric
> field, between the main data table and the lookup table, but this
> dramatically slows down indexing.
I believe SQL JOIN is the fastest and easiest way in your case (in
comparison with nested entity even using CachedSqlEntity). You
probably
: We have a database that has numeric values for some columns, which
: correspond to text values in drop-downs on a website. We need to
: index both the numeric and text equivalents into Solr, and can do
: that via a lookup on a different table from the one holding the
: main data. We are currentl
On Thu, 29 Jul 2010 12:30:50 +0200
Chantal Ackermann wrote:
> Hi Gora,
>
> your suggestion is good.
>
> Two thoughts:
> 1. if both of the tables you are joining are in the same database
> under the same user you might want to check why the join is so
> slow. Maybe you just need to add an index
Hi Gora,
your suggestion is good.
Two thoughts:
1. if both of the tables you are joining are in the same database under
the same user you might want to check why the join is so slow. Maybe you
just need to add an index on a column that is used in your WHERE
clauses. Joins should not be slow.
2.
