Re: Yokozuna error during indexing

2014-11-22 Thread Oleksiy Krivoshey
Thanks, Unfortunately I have few millions of keys in a live application and its almost impossible to update them all without stopping the service. And it can't be as simple as whitespace<->underscore replacement (what if there will be a real underscore in the name?). On 22 November 2014 at 16:15,

Re: Yokozuna error during indexing

2014-11-22 Thread Eric Redmond
Go ahead and submit an issue. We'll take a look at it, but it could be months before a fix ends up in a release. I'd take Ryan's suggestion for now and replace spaces with another char like underscore (_). Eric On Nov 21, 2014, at 11:20 PM, Oleksiy Krivoshey wrote: > Bucket backend is elevel

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
HI Ryan, Thanks! Unfortunately I can't do this on my live application. Is this going to be fixed? Should I submit an issue to Yokozuna project at github? On 22 November 2014 02:02, Ryan Zezeski wrote: > > Oleksiy Krivoshey writes: > > > Got few results: > > > > I don't see anything wrong with t

Re: Yokozuna error during indexing

2014-11-21 Thread Ryan Zezeski
Oleksiy Krivoshey writes: > Got few results: > > I don't see anything wrong with the first record, but the second record > mentions the key '/.Trash/MT03' which is not correct, the correct key that > exists in that bucket is > > '/.Trash/MT03 348 plat frames' > You have found a bug in Yokozuna.

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
There are other keys, that start with the same prefix, e.g.: /.Trash/MT03 348 plat frames/MT03 348 plat 001.jpg /.Trash/MT03 348 plat frames/MT03 348 plat 002.jpg /.Trash/MT03 348 plat frames/MT03 348 plat 003.jpg On 22 November 2014 00:20, Oleksiy Krivoshey wrote: > Bucket backend is

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
Bucket backend is eleveldb. Bucket props are: '{"props":{"backend":"fs_files","allow_mult":"false","r":1,"notfound_ok":"false","basic_quorum":"true","search_index":"files_index"}}' fs_files backend: {<<"fs_files">>, riak_kv_eleveldb_backend, [ % {total_leveldb_mem, 8589934592},

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
Got few results: I don't see anything wrong with the first record, but the second record mentions the key '/.Trash/MT03' which is not correct, the correct key that exists in that bucket is '/.Trash/MT03 348 plat frames' (riak@127.0.0.1)1> redbug:start("yz_solr:to_pair -> return", [{time, 60}

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
I have really basic Erlang knowledge (just a few m/r tasks for Riak). But I definitely would like to try. Give me some information to so that I can start please. Btw, I also have the same problem on my local application setup (on a laptop) with a single Riak node. On 21 November 2014 22:30, Ryan Z

Re: Yokozuna error during indexing

2014-11-21 Thread Ryan Zezeski
Oleksiy Krivoshey writes: > > Entropy Trees > > Index Built (ago) > --- > 114179815416476790484662877555959610

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
Hi Ryan, here is one of the nodes: == Exchanges == Index Last (ago)All (ago) --- 114179815416476790484662877

Re: Yokozuna error during indexing

2014-11-21 Thread Ryan Zezeski
Oleksiy Krivoshey writes: > > Still, what kind of base64 string can it be? I don't have anything base64 > encoded in my data, its a pure JSON objects stored with content_type: > 'application/json' The _yz_* fields (which need to be part of your schema and defined exactly as defined in the defaul

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
Thanks, I'll try to catch it. Still, what kind of base64 string can it be? I don't have anything base64 encoded in my data, its a pure JSON objects stored with content_type: 'application/json' On 21 November 2014 21:53, Ryan Zezeski wrote: > redbug:start("yz_solr:to_pair -> return", [{time, 600

Re: Yokozuna error during indexing

2014-11-21 Thread Ryan Zezeski
Oleksiy Krivoshey writes: > Yes, I'm using custom schema and custom bucket type. There are many (over > 500) buckets of this type. Did you modify any of the _yz_* fields? > Your command have returned the following tuple: > > (riak@10.0.1.1)1> redbug:start("yz_solr:to_pair -> return"). > {1919,1

Re: Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
Yes, I'm using custom schema and custom bucket type. There are many (over 500) buckets of this type. Your command have returned the following tuple: (riak@10.0.1.1)1> redbug:start("yz_solr:to_pair -> return"). {1919,1} redbug done, timeout - 0 How do I get bucket/key/base64_string from this? On

Re: Yokozuna error during indexing

2014-11-21 Thread Ryan Zezeski
Oleksiy Krivoshey writes: > Hi, > > I have enabled Yokozuna on existing Riak 2.0 buckets and while it is still > indexing everything I've already received about 50 errors like this: > > emulator Error in process <0.26807.79> on node 'riak@10.0.1.1' with exit > value: > {{badmatch,false},[{base64,

Yokozuna error during indexing

2014-11-21 Thread Oleksiy Krivoshey
Hi, I have enabled Yokozuna on existing Riak 2.0 buckets and while it is still indexing everything I've already received about 50 errors like this: emulator Error in process <0.26807.79> on node 'riak@10.0.1.1' with exit value: {{badmatch,false},[{base64,decode_binary,2,[{file,"base64.erl"},{line