[ 
https://issues.apache.org/jira/browse/AVRO-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802646#action_12802646
 ] 

Philip Zeyliger commented on AVRO-321:
--------------------------------------

I don't really like missing arguments to rpcsend triggering arbitrary things to 
be sent.  I'd like to use rpcsend as an interactive tool to interact with real 
servers, and adding non-determinism seems not nice for that.  At this point, 
there's enough special behavior; could we just name the tool "interop", and use 
that?  It may share code or behavior with "rpcsend", but I think it would be 
clearer if it the name were independent.

Alternately, I think it's totally fair game to generate or check-in sample data 
(perhaps in AvroDataFile format) to the repo and have a command-line flag that 
reads the input from a file.  That avoids the JSON decoder problem, since the 
file has binary encoded data.

> 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.

Reply via email to