[
https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870827#action_12870827
]
Jeff Hammerbacher commented on AVRO-548:
----------------------------------------
Doug: see AVRO-333. If I get time I'll try to get this into 1.3.3, otherwise it
will have to wait until 1.4.0. I'm traveling right now and don't have tons of
time to page in the testing infrastructure for RPCs and write a new test, but I
want to make sure clients don't have this bug ASAP.
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
> Attachments: AVRO-548.patch
>
>
> In building the Avro server and client for HBase (see
> http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where
> my first RPC from client to server behaves nicely, but the second message
> sent will create two RPCs between the client and server. Not sure if the
> client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of
> the CLIENT match in the handshake. We were telling the requestor that no
> response was present; in fact, a response is present, and should be processed
> as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
