I can interprete your question in 2 different ways: 1. Do you want to index several heterogenous documents all coming from different tables? So documents of type "tableA" are created and indexed alongside documents of type "tableB", "tableC", etc. 2. Do you want to combine unrelated data from 15 tables to form some kind of logical solr-document as your basis for indexing?
I assume you mean nr 1. This can be done, and is done quite regularly. And you're right that this creates a lot of empty slots for fields that only exist for documents created from tableA and not tableB, etc. This in itself is not a problem. In this case I would advise you to create an extra field: 'type' (per the above example with values: (table)A, (table)B, etc. ) So you can distinguish the different types of documents that you have created (and filter on them) . If you meant nr2, which I believe you didn't: it's logically impossible to create/imagine a logical solr-document comprised of combining unrelated data. You should really think about what you're trying to achieve (what is it that I want to index, what do I expect to do with it, etc. ) If you did mean this, please show an example of what you want to achieve. HTH, Geert-Jan 2010/7/29 S Ahmed <sahmed1...@gmail.com> > I understand (and its straightforward) when you want to create a index for > something simple like Products. > > But how do you go about creating a Solr index when you have data coming > from > 10-15 database tables, and the tables have unrelated data? > > The issue is then you would have many 'columns' in your index, and they > will > be NULL for much of the data since you are trying to shove 15 db tables > into > a single Solr/Lucense index. > > > This must be a common problem, what are the potential solutions? >
