Support for ASCII for Protocol for plugin

[steevo590]

I am trying to use the memcached client to talk to hazelcast instead of memcached for doing data enrichment in logstash since hazelcast supports the memcached client it seemed like an easy drop in replacement however hazelcast only supports the ascii protocol and not the binary protocol which the filter currently uses so I'd like the ascii protocol supported as well as the binary.

thanks,

[chavalino]

I support this but for debugging. I'm stuck with an error and can't debug further. The log is not that helpful now. See below.

<27 new auto-negotiating client connection
27: Client using the binary protocol
<27 Read binary protocol data:
<27 0x80 0x0b 0x00 0x00
<27 0x00 0x00 0x00 0x00
message repeated 4 times: [ <27 0x00 0x00 0x00 0x00]

27 Writing bin response:
27 0x81 0x0b 0x00 0x00
27 0x00 0x00 0x00 0x00
27 0x00 0x00 0x00 0x05
27 0x00 0x00 0x00 0x00
message repeated 2 times: [ >27 0x00 0x00 0x00 0x00]
<27 connection closed.

[jgregmac]

For what it's worth, the fairly well known facebook project "mcrouter" also implements only the memcached ASCII protocol. I was feeling pretty excited about implementing mcrouter to address reliability issues with memcached, only to have my bubble burst when I discovered that the logstash memcached plugin is not compatible!

I guess I will need to look to some kind of alternative, as without mcrouter, memcached causing me a LOT of management and reliability headaches.