[
https://issues.apache.org/jira/browse/AVRO-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802504#action_12802504
]
Doug Cutting commented on AVRO-321:
-----------------------------------
The problem with the existing Java command line RPC tools is that they
presuppose a json decoder implementation.
To amend this, I propose that, if request or response data is not specified on
the command line, then the command line tool should generate a random datum and
use that. Similarly, if the message name is not specified, then the client
tool should send a random message from the protocol and the server tool should
respond to any message in the protocol.
The remaining problem is how the server should communicate its port. I propose
that, if the port passed to a server is zero, indicating that a port should be
allocated dynamically, then the server should write the port to standard output
as its first and only line. Then a client shell script can do something like:
{code}
avro-java-tool rpcreceive "http://0.0.0.0:0/" "$protocol" > port &
sleep 1 # wait for server to start & write port
avro-py-tool rpcsend "http://0.0.0.0:`cat port`" "$protocol"
wait # wait for server to exit
{code}
This would generate a random call from Python to Java. The top-level interop
script would do this some number of times for each language pair.
> Run Java RPC interop tests again
> --------------------------------
>
> Key: AVRO-321
> URL: https://issues.apache.org/jira/browse/AVRO-321
> Project: Avro
> Issue Type: Test
> Components: build, java
> Reporter: Jeff Hammerbacher
> Assignee: Doug Cutting
> Fix For: 1.3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.