lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky" <j...@basetechnology.com>
Subject Re: Schema Change: Int -> String (i am the original poster, new email address)
Date Fri, 07 Jun 2013 03:41:13 GMT
Okay, now, how about a few queries that you want to use? Do you want to 
query by parts of the user ID, or only by the whole (exact) value?

If the user ID will be a string, fine, but having spaces makes it a little 
more painful to enter in a query - maybe use dashes.

-- Jack Krupansky

-----Original Message----- 
From: z z
Sent: Thursday, June 06, 2013 11:31 PM
To: solr-user@lucene.apache.org
Subject: Re: Schema Change: Int -> String (i am the original poster, new 
email address)

3. Too hard to say from the way you have described it. Show us some sample
input.

Jack,

Here you go.

*Row X*
column1: "data here"
column2: "more data here"
...
user_id: 2002

*Row Y*
column1: "data here"
column2: "more data here"
...
user_id: 45

*Row Z*
column1: "data here"
column2: "more data here"
...
user_id: 45664

So what I plan on doing before inserting into mysql, which is where solr
pulls the data from, is shrinking similar datasets into one row:

*Single Row XYZ*
column1: "data here"
column2: "more data here"
...
user_id: "2002 45 45664"

Then I would like to have solr parse the user_id as a string.  I just want
to be sure that there wont be any fuzzy searching happening against the
user_id.  That is, 566 shouldn't be a valid value for the user_id list
above.  It has to return exact results based on user ids.  Also I am
wondering if this will affect performance at all, but I am thinking not
because solr is very fast in general.

Regards,
Nate 


Mime
View raw message