Hi Deepthi,
I never tried case with multivalue field.
One note about join - your dictionary index must be single shard index and must
be replicated on all Solr nodes where your other index is.
Let us know how it worked out for you.
Thanks,
Emir
--
Monitoring - Log Management - Alerting - Anomaly
Hi Emir,
Thank you. The dictionary is static but the descriptions are long text. If
i denormalize each document will have 100+ descriptions and I have 8
million records in collection. There is lot of repetition of descriptions
and the index becomes large. I am trying to avoid that. Also data load
Hi Deepthi,
Is dictionary static? Can value for some id change? If static, and if query
performance matters to you, the best and also the simplest solution is to
denormalise data and store dictionary values with docs.
Alternative is to use join query parser:
https://lucene.apache.org/solr/guide
: - We are indexing CSV files and generating field names dynamically from the
: "header" line.
: User should be able to *list all the possible header names* (i.e. dynamic
: field names), and filter results based on some of the field names.
: - Also, list* all possible values* associated to for a g
First Thanks for the response.
Yes, mostly likely we want to optimize to one index file. I think it is
possible, coming from the RDBMS world we might be over complicating the
solution.
*Requirement:*
- We are indexing CSV files and generating field names dynamically from the
"header" line.
User
On Sat, Jan 16, 2010 at 3:33 AM, Kumaravel Kandasami <
kumaravel.kandas...@gmail.com> wrote:
> Need to your suggestion in best designing the following requirement.
>
> - We have two indexes.
> Index 1: "name_index",
> Fields:
> "id" - indexed, not stored
> "field_name" - indexed, stored.
>
> Ind
