Re: Link walking with a java client

Created bug 1341 to track this. Can you help me with the questions below ? I am trying to gauge how expensive linking is in comparison to using a secondary index to track a node. Thanks Deepak On Wed, May 30, 2012 at 9:42 AM, Deepak Balasubramanyam

Re: Link walking with a java client

Brian, Yes I read about the hack somewhere in your documentation. My understanding is that the link walking operation will cease to work via HTTP after links to a node grow beyond a particular number. This happens because a HTTP header is used to send link related data and there are limits around

Re: Link walking with a java client

Deepak - I'll take a look at it this week, but more than likely it's a bug. Link walking is a REST only operation as far as Riak’s interfaces are concerned. Link Walking in the protocol buffers Java client is a hack that issues two m/r jobs to the protocol buffers interface (the first construct

Re: Link walking with a java client

This looks like a bug. The code to walk links via a HTTP client works perfectly. The same code fails when the PB client is used. The POJO attached in this email reproduces the problem. I searched the email archives and existing issues and found no trace of this problem. Please run the POJO by swap