Hi everyone, My solution requires that users in group-A can only search against a set of fields-A and users in group-B can only search against a set of fields-B, etc. There can be several groups, as many as 100 even more. To meet this need, I build my search by passing in the list of fields via "qf". What goes into "qf" can be large: as many as 1500 fields and each field name averages 15 characters long, in effect the data passed via "qf" will be over 20K characters.
Given the above, beside the fact that a search for "apple" translating to a 20K characters passing over the network, what else within Solr and Lucene I should be worried about if any? Will I hit some kind of a limit? Will each search now require more CPU cycles? Memory? Etc. If the network traffic becomes an issue, my alternative solution is to create a /select handler for each group and in that handler list the fields under "qf". I have considered creating pseudo-fields for each group and then use copyField into that group. During search, I than can "qf" against that one field. Unfortunately, this is not ideal for my solution because the fields that go into each group dynamically change (at least once a month) and when they do change, I have to re-index everything (this I have to avoid) to sync that group-field. I'm using "qf" with edismax and my Solr version is 5.1. Thanks Steve
