Github user MikeThomsen commented on the issue:
    @markap14 Ok, that's fair. I think the general issue has to be addressed, 
but the easy route is obviously blocked. So what I'm going to do to try to head 
this is off is:
    1. Rip out the changes to the 5x client and keep the 6x version.
    2. Add some metadata to the 5x client service to help provide some visual 
cues in the UI.
    3. See if there is a way to get the protocol compatibility range from the 
ES client API. I've seen debug info that suggests it looks for that and 
enforces it, so I'm hoping there's a client API which will let us sniff that 
and throw an error saying you need to change client services to keep w/ ES 
protocol compatibility.


Reply via email to