@Rohit you can look into this.
http://www.javaworld.com/article/2074996/hashcode-and-equals-method-in-java-object---a-pragmatic-concept.html
A good article for hashcode and equals
--
View this message in context:
http://lucene.472066.n3.nabble.com/Sorting-Problem-with-custom-ValueSourceParser
I tried returning false in equals method but still it has no effect.
Btw is there any documentation where i can look at what the functions are
used for. I can't find any proper documentation related to it. It is very
difficult to guess the usage of the functions.
I don't think it will be a good i
Hi Hoss,
Thanks for the response. Will make the necessary changes and get back to
you.
Btw this is just a testing code. The logic is yet to be implemented. What
according to you could be the best way to return hashcode?
Regards,
Rohit
On Oct 5, 2016 5:27 AM, "Chris Hostetter" wrote:
>
> : Eg:
: Eg: if i make a query to sort by func(cost) desc
: It works.
: Now if i change cost with some another field eg func(rating) desc
: It sorts the result by cost only.
:
: Now if i restart the solr server and call sort by func(rating) it works but
: now it will stick with rating
:
: Any idea why
Take a look at Solr's use of DocValues:
https://cwiki.apache.org/confluence/display/solr/DocValues.
There are docValues options that use less memory then the FieldCache.
Joel Bernstein
Search Engineer at Heliosearch
On Thu, May 15, 2014 at 6:39 AM, Jeongseok Son wrote:
> Hello, I'm struggling
> > Does anyone know what could be the problem?
> >
>
> looks like it was a problem in the new query parser. I just fixed it
> in trunk:
> http://svn.apache.org/viewvc?view=rev&revision=592740
Thanks it works now.
Cheers,
Michael
--
Michael Thessel <[EMAIL PROTECTED]>
Gossamer Threads Inc. h
On 11/7/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> Yonik - do we want to keep this checking for 'null', or should we change
> QueryParser.parseSort( ) to always return a valid sortSpec?
In Lucene, a null sort is not equal to "score desc"... they result in
the same documents being returned, but
Does anyone know what could be the problem?
looks like it was a problem in the new query parser. I just fixed it in
trunk:
http://svn.apache.org/viewvc?view=rev&revision=592740
Yonik - do we want to keep this checking for 'null', or should we change
QueryParser.parseSort( ) to always retu
Yonik Seeley wrote:
On 11/7/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Yonik - do we want to keep this checking for 'null', or should we change
QueryParser.parseSort( ) to always return a valid sortSpec?
In Lucene, a null sort is not equal to "score desc"... they result in
the same documents
Thank you, Hoss...
> -Original Message-
> From: Chris Hostetter [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 08, 2007 8:41 PM
> To: solr-user@lucene.apache.org; [EMAIL PROTECTED]
> Subject: Re: sorting problem
>
>
> : My query tries to search all entries wh
: My query tries to search all entries which their ctype is video sorted by
: tstamp descending and then sorted by popularity:
: However the results returned are sorted only by the tstamp.
Solr stores datefields with millisecond precision, so if you index a date
field without rounding, then all
11 matches
Mail list logo