On Mon, Oct 27, 2014 at 11:18 AM, Camp, Jonathan
wrote:
> But you say that this objfsptr def is valid?
>
> [{'name': 'objfsptr',
> 'type': {'fields': [{'name': 'uri', 'type': 'string'}],
>'name': 'ObjFSPtr',
>'namespace': 'FooServiceType',
>'type': 'record'}}]
'type': 'record'}}]
Is this also valid? Identical?
[{'name': 'objfsptr',
'fields': [{'name': 'uri', 'type': 'string'}],
'name': 'ObjFSPtr',
'namespace': 'FooServiceType&
The type of the objfsptr parameter looks correct to me. Rather than a
reference to the name of the record it has the record's definition.
What looks incorrect about this to you?
That said, I have no idea what's causing that error.
Doug
On Sun, Oct 26, 2014 at 12:20 PM, Camp, Jonathan
wrote:
>
Hi All, I am trying to use avro's protocol definition to provide the basis for
an RPC system. In this case, I'll be handling the handshaking and transport
layer rather the avro's IPC package. Are the schemas generated from the
protocol files compatible with the standard DataFileWriter/Reader sch