Re: trivia question: why q=*:* doesn't return same result as q.alt=*:*

As Chris explained, this is special: q=*:* in terms of scoring or anything of the like. It's just match-all-docs It makes no sense to distribute *:* among "pf" fields. The whole point of pf is to influence scoring by providing a mechanism for boosting when words in some field(s) appear together

Re: trivia question: why q=*:* doesn't return same result as q.alt=*:*

Thanks everyone, that was a very informative thread. One more curiosity: why are different set of fields being used based on the query string:- http://localhost:8983/solr/filesearch/select?fq=id:1193; q=*:*=true - parsedquery: "+DisjunctionMaxQuery((user_email:*:* | user_name:*:* |

Re: trivia question: why q=*:* doesn't return same result as q.alt=*:*

: Yes, i am using dismax. But dismax allows *:* for q.alt ,which also seems : like inconsistency. dismax is a *parser* that affects how a single query string is parsed. when you use defType=dismax, that only changes how the "q" param is parsed -- not any other query string params, like "fq" or

Re: grouping in solr cloud shard replicas

On 1/6/2018 11:25 AM, SANJAY. wrote: Please let me know how to achieve group by in solr could env. We tried grouping in solr cloud shard replicas to fetch unique search result from solr for custom field we . we are getting exception saying unexpected docvalues type "SORTED_SET (expected

grouping in solr cloud shard replicas

Hi, Please let me know how to achieve group by in solr could env. We tried grouping in solr cloud shard replicas to fetch unique search result from solr for custom field we . we are getting exception saying unexpected docvalues type "SORTED_SET (expected SORTED)" We are using solr cloud and

Re: Personalized search parameters

Don't we need vectors of the same size to calculate the cosine similarity? Maybe I missed something, but following that example it looks like i have to manually recreate the sparse vectors, because the term vector of a document should (i may be wrong) contain only the terms that appear in that

Re: trivia question: why q=*:* doesn't return same result as q.alt=*:*

On 1/5/2018 7:22 PM, Nawab Zada Asad Iqbal wrote: Yes, i am using dismax. But dismax allows *:* for q.alt ,which also seems like inconsistency. It works in q.alt because q.alt is interpreted using the standard (lucene) query parser. The dismax parser doesn't understand lucene syntax like

Re: Deliver static html content via solr

On 1/5/2018 6:26 PM, Rick Leir wrote: Erik, Sorry I didn't mean to say Velocity has a security problem. I am just thinking that people will see it in action and think it is a full answer to a front end web app, though it has no input filtering or range checking ( as an output template system,

Re: No match when querying but in admin/analysis it works!! (schema, indexed data and screen shots are provided)

Thank Erick. Your thoughts are correct and solved the problem. I appreciate you looking at my problem and sorry for the late reply. Of course, providing enough data, evidence that I've tried to solve it and easy to understand problem structure are very important in order to encourage others and

Re: Personalized search parameters

Maybe I misunderstood the question, but why you need to create the full size vectors? can't you just compute the cosine using the sparse vectors? On Fri, Jan 5, 2018 at 10:09 PM, marco wrote: > At the moment I have another problem: is there an efficient way to calculate