Jack Krupansky wrote: > In general, Solr is much more friendly towards static data models. Yes, you > can use dynamic fields, but use them in moderation. The more heavily you > lean on them, the more likely that you will eventually become unhappy with > Solr.
Can you concrete examples of what kinds of issues should I expect to face when using a data model with only dynamic fields? We've requirements that quite explicitly direct us into using dynamic fields and I'd like to understand what kinds of problems we might end up having. > How many fields are we talking about here? The data model is designed to be dynamic, so the number is not fixed, but I'm expecting there'll be perhaps about 20-40 fields. > The trick with Solr is not to brute-force flatten your data model (as you > appear to be doing), but to REDESIGN your data model so that it is more > amenable to a flat data model, and takes advantage of Solr's features. You > can use multiple collections for different types of data. And you can > simulate joins across tables by doing a sequence of queries (although it > would be nice to have a SolrJ client-side method to do that in one API > call.) We're storing arbitrarily complex object graphs in a data store and want to use Solr for implementing search property field search. It may be difficult to use a flatter data model, but I'll consider this option as well. thanks! marko
