Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

Unsubscribe On Sat, Dec 28, 2019 at 11:29 roger peppe wrote: > > > On Sat, 21 Dec 2019, 17:09 Vance Duncan, wrote: > >> I suggest naming the timestamp field "timestamp" rather than "time". You >> might also want to consider calling it "eventTimestamp", since there will >> possibly be the need

Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

On Sat, 21 Dec 2019, 17:09 Vance Duncan, wrote: > I suggest naming the timestamp field "timestamp" rather than "time". You > might also want to consider calling it "eventTimestamp", since there will > possibly be the need to distinguish when the event occurred vs. when it was > actually

Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

I suggest naming the timestamp field "timestamp" rather than "time". You might also want to consider calling it "eventTimestamp", since there will possibly be the need to distinguish when the event occurred vs. when it was actually published, due to delays in batching, intermittent downtime, etc.

Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

Actually, having looked a bit closer, I think I get the gist of what you're saying (though the IDL spec doesn't seem to mention the @logicalType form, so I'm still guessing somewhat). I'd certainly considered that approach. Essentially you seem to

Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

Hi, Excuse my ignorance, but I'm not at all familiar with IDL. Is there an easy way to translate it to a JSON Avro schema, please? (preferably online :)) cheers, rog. On Fri, 20 Dec 2019 at 21:06, Zoltan Farkas wrote: > Hi Roger, > > have you considered leveraging avro logical types,

Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

Hi Roger, have you considered leveraging avro logical types, and keep the payload and event metadata “separate”? Here is a example (will use avro idl, since that is more readable to me :-) ): record MetaData { @logicalType(“instant") string timeStamp; ….. all the meta data

Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

On Thu, 19 Dec 2019 at 10:11, Ryan Skraba wrote: > Hello! You might be interested in this short discussion on the dev@ > mailing list: > https://lists.apache.org/x/thread.html/dd7a23c303ef045c124050d7eac13356b20551a6a663a79cb8807f41@%3Cdev.avro.apache.org%3E > > In short, it appears that the

Re: name-agnostic schema resolution (a.k.a. structural subtyping?)

Hello! You might be interested in this short discussion on the dev@ mailing list: https://lists.apache.org/x/thread.html/dd7a23c303ef045c124050d7eac13356b20551a6a663a79cb8807f41@%3Cdev.avro.apache.org%3E In short, it appears that the record name is already ignored in record-to-record matching

name-agnostic schema resolution (a.k.a. structural subtyping?)

Hi, Background: I've been contemplating the proposed Avro format in the CloudEvent specification , which defines standard metadata for events. It defines a very generic format for an event that allows storage of almost any data. It