Tihomir Krasimirov Mateev
Tihomir Krasimirov Mateev
Sooo folks I'd love to hear from you what you think about the latest solution. I already had a discussion with @uglide on that, but would love to hear any...
> The new output is pretty complex and its result seems pretty complex to understand as well. A `Object` or `List` return is typically much easier to consume as it...
> We should return Map to make the response usable even without a parser. @uglide what is your take on this solution?
ping @uglide :)
Everyone, after a 30min discussion with @atakavci I realized we are definitely over-engineering this and only making it complex to the users of the driver as a result. The final...
> Hiding the inner `Output` is a good thing and it will allow for future revision without breaking calling code. I would strongly advise to investigate on a generic output...
Just for the sake of argument (I mostly agree with your comments): > * i think using a new version of client api with an old version of server is...
Hey @zafir-zhong , are you sure this issue does not belong to the [spring-data-redis](https://github.com/spring-projects/spring-data-redis)? From the information you've provided it is hard to understand what is going wrong. Could you...
> Can you provide some suggestions on when Lettuce may throw this exception? Now all I know is that the service malfunctioned after receiving a Redis message This message means...
> I am unable to reproduce this issue stably, but it always occurs sporadically.And, in the exception stack, only the relevant information of Lettuce can be seen. it happen when...