Re: Document Security Model Question

Thanks Rajinimaski for the reposnse. Agree that if the changes are frequent, then first option wouldn't work efficiently. Also the other challenge is that in our case for each resource, it is easy/efficient to get a list of changes since last checkpoint (because of our model of deployment of cust

Re: Indexing different customer customized field values

Thanks Otis We also thought about having multiple fields, but thought that having too many fields will be an issue. I see threads about too many fields is an issue for sort (we don't expect to sort on these), but look through the archives. -- View this message in context: http://lucene.4720

Indexing different customer customized field values

In our application, we index educational resources and allow searching for them. We allow our customers to change some of the non-textual metadata associated with a resource (like booklevel, interestlevel etc) to serve their users better. So for each resource, in theory it could have different set

Document Security Model Question

I had earlier posted a similar discussion in LinkedIn and David Smiley rightly advised me that solr-user is a better place for technical discussions -- Our product which is hosted supports searching on educational resources. Our customers can choose to make specifi

Use BM25Similarity for title field and default for others

We want the effect of the field length to have a lesser influence on score for the title field (we don't want to completely disable it) -- so we get the following behavior Docs with more hits in the title rank higher Docs with shorter titles rank higher if the hits are equal. The DefaultS