Right, a search for "442" would not match "1442".
-- Jack Krupansky
-Original Message-
From: z z
Sent: Friday, June 07, 2013 2:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Schema Change: Int -> String (i am the original poster, new
email address)
Mayb
Maybe if I were to say that the column "user_id" will become "user_ids"
that would clarify things?
user_id:2002+AND+created:[${**from}+TO+${until}]+data:"more"
becomes
user_id*s*:2002+AND+created:[${**from}+TO+${until}]+data:"more"
where I want 2002 to be an exact positive match on one of the u
nts and your data model,
> including a clarification about user id vs. "a string of concatenated user
> id values", I can't answer your question definitively, other than "Maybe,
> depending on what you really mean by user id."
>
>
> -- Jack Krupansky
>
>
ion definitively, other than "Maybe,
depending on what you really mean by user id."
-- Jack Krupansky
-Original Message-
From: z z
Sent: Friday, June 07, 2013 12:11 AM
To: solr-user@lucene.apache.org
Subject: Re: Schema Change: Int -> String (i am the original poster, new
The unique key is an auto-incremented int in the db. Sorry for having
given the impression that user_id is the unique key per document. This is
a table of events that are happening as users interact with our system.
It just so happens that we were inserting individual records for each user
before
2013 11:48 PM
To: solr-user@lucene.apache.org
Subject: Re: Schema Change: Int -> String (i am the original poster, new
email address)
I want to query against one user_id in the string.
eg user_id:2002+AND+created:[${from}+TO+${until}]+data:"more"
So all of the records with a 2002 in us
eg user_id:2002+AND+created:[${from}+TO+${until}]+data:"more"
Expected results: return row "XYZ" but ignore this row:
column1: "data here"
column2: "more data here"
...
user_id: "45 15001 45664"
> *Row X*
>
> column1: "data here"
> column2: "more data here"
> ...
> user_id: 2002
>
> *Row Y*
-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
I want to query against one user_id in the string.
eg user_id:2002+AND+created:[${from}+TO+${until}]+data:"more"
So all of the records with a 2002 in user_id need to be returned and only
those records. If this can only be guaranteed by having user_id be an
integer, then that is fine, but I woul
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
rg
Subject: Schema Change: Int -> String
1) If I change one field's type in my schema, will that cause problems with
the index or searching? My data is pulled in chunks off of a mysql server
so one field in the currently indexed data is simply an "int" type field in
solr. I would lik
On 6/5/2013 11:25 PM, TwoFirst TwoLast wrote:
> 1) If I change one field's type in my schema, will that cause problems with
> the index or searching? My data is pulled in chunks off of a mysql server
> so one field in the currently indexed data is simply an "int" type field in
> solr. I would lik
1) If I change one field's type in my schema, will that cause problems with
the index or searching? My data is pulled in chunks off of a mysql server
so one field in the currently indexed data is simply an "int" type field in
solr. I would like to change this to a string moving forward, but still
13 matches
Mail list logo
