On 7/1/2014 8:43 AM, Koji Sekiguchi wrote:
In addition, KeywordTokenizer can be seemingly used but it should be
avoided
for unique key field. One of my customers that used it and they had got OOM
during a long term indexing. As it was difficult to find the problem,
I'd like to share my
No, you definitely can have an int or long uniqueKey. A lot of Solr's tests
use such a uniqueKey. See
solr/core/src/test-files/solr/collection1/conf/schema.xml
On Tue, Jul 1, 2014 at 3:20 PM, Alexandre Rafalovitch arafa...@gmail.com
wrote:
Hello,
I remember reading somewhere that id field
Alex, maybe you're thinking of constraints put on shard keys?
Michael Della Bitta
Applications Developer
o: +1 646 532 3062
appinions inc.
“The Science of Influence Marketing”
18 East 41st Street
New York, NY 10017
t: @appinions https://twitter.com/Appinions | g+:
plus.google.com/appinions
I wasn't thinking of shard keys, but may have been confused in the reading.
Thank you everyone, the long key is working just fine for me.
Regards,
Alex.
Personal website: http://www.outerthoughts.com/
Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency
On Tue,
In addition, KeywordTokenizer can be seemingly used but it should be avoided
for unique key field. One of my customers that used it and they had got OOM
during a long term indexing. As it was difficult to find the problem,
I'd like to share my experience.
Koji
--
non-String uniqueKey fields have historically popped out
in weird places. I think at one point, for instance,
QueryElevationComponent barfed on non-string types.
So, there may still be edge cases in which this can be a problem.
IMO, they're all bugs though.
Erick
On Tue, Jul 1, 2014 at 7:43 AM,
: Re: Restriction on type of uniqueKey field?
I wasn't thinking of shard keys, but may have been confused in the reading.
Thank you everyone, the long key is working just fine for me.
Regards,
Alex.
Personal website: http://www.outerthoughts.com/
Current project: http://www.solr-start.com
