fit in the PDF format.
-- Jack Krupansky
-Original Message-
From: Erick Erickson
Sent: Friday, August 02, 2013 7:23 AM
To: solr-user@lucene.apache.org
Subject: Re: uniqueKey: string vs. long integer
And last I knew (admittedly a long time ago) Query Elevation Component
would fail with a
> > From: Jack Krupansky [mailto:j...@basetechnology.com]
> > Sent: Thursday, August 01, 2013 9:27 AM
> > To: solr-user@lucene.apache.org
> > Subject: Re: uniqueKey: string vs. long integer
> >
> > Although I cringe at the thought of anybody using anything o
gt; Thanks
> Robi
>
> -Original Message-
> From: Jack Krupansky [mailto:j...@basetechnology.com]
> Sent: Thursday, August 01, 2013 9:27 AM
> To: solr-user@lucene.apache.org
> Subject: Re: uniqueKey: string vs. long integer
>
> Although I cringe at the thought of a
Robi
-Original Message-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Thursday, August 01, 2013 9:27 AM
To: solr-user@lucene.apache.org
Subject: Re: uniqueKey: string vs. long integer
Although I cringe at the thought of anybody using anything other than a string
for the uniqu
I mean, is the
key used in numeric calculations? Can it be negative? Is it ever sorted?
But as a Solr best practice, I'd advise against it.
-- Jack Krupansky
-Original Message-
From: Ali, Saqib
Sent: Thursday, August 01, 2013 12:02 PM
To: solr-user@lucene.apache.org
Subject: u
We have an application that was developed by a third party. It
uses uniqueKey that is a long integer instead of a string. Will there be
any repercussions of using a long integer instead of string for the
uniqueKey?
Thanks! :)
