Walter Underwood [mailto:wun...@wunderwood.org] writes:
>On Mar 5, 2012, at 1:16 PM, Welty, Richard wrote:
>> Walter Underwood [mailto:wun...@wunderwood.org] writes:
>>> You may be able to have unique keys. At Netflix, I found that there were
>>> collisions between the movie IDs and the person
On Mar 5, 2012, at 1:16 PM, Welty, Richard wrote:
> Walter Underwood [mailto:wun...@wunderwood.org] writes:
>
>> You may be able to have unique keys. At Netflix, I found that there were
>> collisions between >the movie IDs and the person IDs. So, I put an 'm' at
>> the beginning of each movie I
Walter Underwood [mailto:wun...@wunderwood.org] writes:
>You may be able to have unique keys. At Netflix, I found that there were
>collisions between >the movie IDs and the person IDs. So, I put an 'm' at the
>beginning of each movie ID and a >'p' at the beginning of each person ID. Like
>ma
You may be able to have unique keys. At Netflix, I found that there were
collisions between the movie IDs and the person IDs. So, I put an 'm' at the
beginning of each movie ID and a 'p' at the beginning of each person ID. Like
magic, I had unique IDs.
You should be able to disable the query el
i googled and found numerous references to this, but no answers that went to my
specific issues.
i have a solr 3.5.0 server set up that needs to index several different
document types, there is no common unique key field. so i can't use the
uniqueKey declaration and need to disable the QueryEle