Julio, This is to convert the 1:n and m:n relationships in a DB to multivalued fields in solr. A single sql query ends up giving a 2D matrix where each cell holds one value. It would be harder to denormalize and extract the multivalued fields from a single result set. Check the architecture to see the flow (http://wiki.apache.org/solr/DataImportHandler#arch) --Noble
On Thu, May 22, 2008 at 10:41 AM, Shalin Shekhar Mangar <[EMAIL PROTECTED]> wrote: > Hi Julio, > > Entities are nested when they have parent-child relationships as in a > SQL Join. For example, if your product has categories, you will create > an entity for products and a child entity for categories. However, if > your entities are totally independent of each other, then you can keep > them all at the same level. Remember that the number of documents > created in Solr will be equal to the sum of number of rows for each > root-level entity. > > On Thu, May 22, 2008 at 10:28 AM, Julio Castillo > <[EMAIL PROTECTED]> wrote: >> I'm trying to configure a document config file using the example >> data-config.xml mentioned in the wiki. >> >> One question I have is when to nest the entity tags/nodes in the xml file? >> The proposed example has them nested as >> <document> >> <entity> >> <entity> >> </entity> >> <entity> >> </entity> >> </entity> >> </document> >> >> Why didn't the example had a flatter organization? >> <document> >> <entity> >> </entity> >> <entity> >> </entity> >> ... >> </document> >> >> Julio Castillo >> Edgenuity Inc. >> >> > > > > -- > Regards, > Shalin Shekhar Mangar. > -- --Noble Paul
