Hi Folks, I'm trying to propose Afro for a project I've been drafted on to. Namespace declarations are important... and a requirement is that namespaces are dynamic in nature... preferably even decided at runtime. Is this possible in Avro? Thanks Lewis
Need more info — you can use the Schema builder to do anything you like at runtime, Schema.createRecord and setFields.
On May 5, 2014, at 3:54 PM, Lewis John Mcgibbney <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Hi Folks, I'm trying to propose Afro for a project I've been drafted on to. Namespace declarations are important... and a requirement is that namespaces are dynamic in nature... preferably even decided at runtime. Is this possible in Avro? Thanks Lewis
Hi Sean, Arggggh... Maybe I can propose a change to the namespace semantics in my project. I've been given the following brief. Data files should have a logical namespace structure which can be globally unified across multiple instruments and receiver platforms into a common namespace on the filesystem. I have a whole list of other data representation constraints and Avro satisfies them all. This one is the only 'issue'. Thanks for your help. Lewis On May 5, 2014 4:21 PM, "Sean Busbey" <busbey+[EMAIL PROTECTED]> wrote:
Hi Sean thanks for the additional info. This is really helpful. Some of these constraints are not what I would prefer... and of course mean more work. Powers that be request them ;) Thanks On May 6, 2014 9:06 AM, "Sean Busbey" <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext