For more discussion of best practices for storing Avro-serialized data structures in a database, see http://www.quora.com/What-is-the-best-way-to-work-with-Avro-serialized-data-structures-in-a-database .
On Thu, Sep 16, 2010 at 9:41 AM, Doug Cutting <[email protected]> wrote: > On 09/16/2010 09:25 AM, Scott Carey wrote: > >> Generally, Avro recommends storing the schema with the data. For a >> file that means in the header of the file, for a key/value store that >> means in some system metadata. Any individual store can only keep >> data serialized with one schema. >> > > Another good pattern is to store the hashcode of the writer's schema with > each written instance, then keep written schemas in a separate store, keyed > by hashcode. For example, Sam Pullara's done this in his HAvroBase: > > > http://www.javarants.com/2010/06/30/havrobase-a-searchable-evolvable-entity-store-on-top-of-hbase-and-solr/ > > Doug >
