[
https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher updated AVRO-548:
-----------------------------------
Summary: Python client should handle CLIENT handshake match status
correctly (was: Investigate why Python client feels need to send message twice
to Java server once protocol has been cached)
Description:
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.
was: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.
> 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
>
> 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.
