{"shas":[["60ad199c96ca79db38e1e4124de250f140fdc6b6","d572df6721019ddaf13014819c38f402030deb5d@redjack.com","Consume avro_datum_t instances\n\nYou can now send the contents of an avro_datum_t instance into a\nconsumer object.  Along with the resolver consumers, this lets you\nchange the schema of a datum, according to the schema resolution rules.","Douglas Creager"],["4bab81fce013a2f4f90d9e8fb2abd2850a35c3c4","d572df6721019ddaf13014819c38f402030deb5d@redjack.com","Child consumers in base consumer class\n\nBefore, the resolver subclass maintained a list of “child” consumers,\nwhich would be used to store the resolvers for each field in a record,\nelement in an array, etc.  While working on the schema-specific\nresolvers, it turned out that this is a common need, so we've moved this\narray into the base consumer class.  The avro_consumer_free() function\ntakes care of recursively freeing any child consumers in the array.  We\nallow consumer cycles in the array, so that we can support recursive\nschemas easily; the avro_consumer_free() function also takes care of\nensuring that each consumer in a cycle is freed only once.","Douglas Creager"],["88645caec1cdc6eaa4c1e01a2dbdbbff86845bad","d572df6721019ddaf13014819c38f402030deb5d@redjack.com","Encoding consumer\n\nThis patch adds two new implementations of the avro_consumer_t\ninterface.  The first encodes a datum into an avro_writer_t, taking the\nplace of avro_write_data.  The second returns the size of an encoded\ndatum, taking the place of avro_size_data.  Both work on anything that\ncan send Avro data into a consumer, and so they're not limited to\navro_datum_t instances.","Douglas Creager"]],"ref":"refs/heads/dcreager-mods","size":3,"head":"88645caec1cdc6eaa4c1e01a2dbdbbff86845bad","push_id":33329260}