Re: SolrCloud FunctionQuery inconsistency

2013-12-06 Thread sling
message in context: http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346p4105293.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: SolrCloud FunctionQuery inconsistency

2013-12-05 Thread Shawn Heisey
On 12/5/2013 2:27 AM, sling wrote: > By the way, the "shards" param is running ok with the value > "localhost:7574/solr,localhost:8983/solr" or "shard2", > but it get an exception with only one replica "localhost:7574/solr"; > > right: > shards=204.lead.index.com:9090/solr/doc/,66.index.com:8080

Re: SolrCloud FunctionQuery inconsistency

2013-12-05 Thread sling
m:8080/solr/doc/ wrong: shards=204.lead.index.com:9090/solr/doc/ why can't this param run with only one replica? -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346p4105078.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: SolrCloud FunctionQuery inconsistency

2013-12-04 Thread Chris Hostetter
: There is no default value for ptime. It is generated by users. thank you, that rules out my previous wild guess. : I was trying query with a function query({!boost b=dateDeboost(ptime)} : channelid:0082 && title:abc), which leads differents results from the same : shard(using the param: shards

RE: SolrCloud FunctionQuery inconsistency

2013-12-04 Thread sling
Hi Raju, Collection is a concept in solrcloud, and core is in standalone mode. So you can create multiple cores in solr standalone mode, not collections. -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346p4104888.html Sent from

RE: SolrCloud FunctionQuery inconsistency

2013-12-03 Thread Raju Shikha
.. Regards, Raju Shikha -Original Message- From: sling [mailto:sling...@gmail.com] Sent: 04 December 2013 08:33 To: solr-user@lucene.apache.org Subject: Re: SolrCloud FunctionQuery inconsistency Thanks, Chirs: The schema is: There is no default value for ptime. It is generated by

Re: SolrCloud FunctionQuery inconsistency

2013-12-03 Thread sling
has not synced from its leader? so if query from different nodes from the shard at the same time, it shows different results. -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346p4104851.html Sent from the Solr - User mailing list

Re: SolrCloud FunctionQuery inconsistency

2013-12-03 Thread Chris Hostetter
: Yes, I am populating "ptime" using a default of "NOW". : : I only store the id, so I can't get ptime values. But from the perspective : of business logic, ptime should not change. if you are populating it using a *schema* default then the warning text i pasted into my last message would defini

Re: SolrCloud FunctionQuery inconsistency

2013-12-02 Thread sling
e test case... -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346p4104558.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: SolrCloud FunctionQuery inconsistency

2013-12-02 Thread sling
consistent. But for the same query, it shows diffenents sort(either sort A or sort B) over and over. Thanks, sling -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346p4104549.html Sent from the Solr - User mailing list archive at

Re: SolrCloud FunctionQuery inconsistency

2013-12-02 Thread Chris Hostetter
: However, when sort by "ptime desc", the result is consistent. : The dateDeboost generate the time-weight from ptime, which is multiplied by : the score. As Erick mentioned, you haven't given us enough details to make any educated guesses as to what problem you are seeing. My wild, uneducated,

Re: SolrCloud FunctionQuery inconsistency

2013-12-02 Thread Erick Erickson
"params":{ > "fl":"id", > "shards":"shard3", > "cache":"false", > "indent":"true", > "start":"0", > "q":"{!boost b=dateDeboost(ptime)}channelid:0082 && (title:\"abc\" || > dkeys:\"abc\")", > "wt":"json", > "rows":"5"}}, > "response":{"numFound":121,"start":0,"maxScore":0.5319117,"docs":[ > { > "id":"9EOPQGOI00824IMP"}, > { > "id":"9EORHN5I00824IHR"}, > { > "id":"9EMATM6900824IHR"}, > { > "id":"9EJLBOEN00824IHR"}, > { > "id":"9E1LP3S300824IHR"}] > }} > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346.html > Sent from the Solr - User mailing list archive at Nabble.com. >

SolrCloud FunctionQuery inconsistency

2013-12-02 Thread sling
quot;shards":"shard3", "cache":"false", "indent":"true", "start":"0", "q":"{!boost b=dateDeboost(ptime)}channelid:0082 && (title:\"abc\" || dkeys:\"abc\")", "wt":"json", "rows":"5"}}, "response":{"numFound":121,"start":0,"maxScore":0.5319117,"docs":[ { "id":"9EOPQGOI00824IMP"}, { "id":"9EORHN5I00824IHR"}, { "id":"9EMATM6900824IHR"}, { "id":"9EJLBOEN00824IHR"}, { "id":"9E1LP3S300824IHR"}] }} -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-FunctionQuery-inconsistency-tp4104346.html Sent from the Solr - User mailing list archive at Nabble.com.