On Dec 29, 2009, at 2:19 PM, A. Steven Anderson wrote: > Greetings! > > Is there any significant negative performance impact of using a > dynamicField?
There can be an impact if you are searching against a lot of fields or if you are indexing a lot of fields on every document, but for the most part in most applications it is negligible. > > Likewise for multivalued fields? No. Multivalued fields are just concatenated together with a large position gap underneath the hood. > > The reason why I ask is that our system basically aggregates data from many > disparate data sources (structured, unstructured, and semi-structured), and > the management of the schema.xml has become unwieldy; i.e. we currently have > dozens of fields which grows every time we add a new data source. > > I was considering redefining the domain model outside of Solr which would be > used to generate the fields for the indexing process and the metadata (e.g. > display names) for the search process. > > Thoughts? It probably can't hurt to be more streamlined, but without knowing more about your model, it's hard to say. I've built apps that were totally dynamic field based and they worked just fine, but these were more for discovery than just pure search. In other words, the user was interacting with the system in a reflective model that selected which fields to search on. -Grant -------------------------- Grant Ingersoll http://www.lucidimagination.com/ Search the Lucene ecosystem using Solr/Lucene: http://www.lucidimagination.com/search
