Amit - unless you test it would not be apparent. Key piece is as Otis mentioned "flatten everything". This requires effort from your side to actually create documents in manner suitable for your searches. The relationship needs to be "merged" into the document. To avoid storing text representations - you may want to store just the "identifier" and use front end to translate between human readable text vs stored identifier. Taking your case further - Rather than storing ADMIN store just a representation may be a smallint with customer information.
On Wed, Jun 23, 2010 at 11:30 AM, amit_ak <amit...@mindtree.com> wrote: > > Hi Otis, Thanks for the update. > > My paramteric search has to span across customer table and 30 child tables. > We have close to 1 million customers. Do you think Lucene/Solr is the right > fsolution for such requirements? or database search would be more optimal. > > Regards, > Amit > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Nested-table-support-ability-tp905253p916087.html > Sent from the Solr - User mailing list archive at Nabble.com. >
