Re: [Dev] Issue in representing avro records with multiple namespaces

+1 for using "attr_" . On Wed, Mar 2, 2016 at 11:35 AM, Sohani Weerasinghe wrote: > Thanks for the input. Let's use - "name" : "attr_gender" > > Sohani Weerasinghe > Software Engineer > WSO2, Inc: http://wso2.com > > Mobile : +94 716439774 > Blog

Re: [Dev] Issue in representing avro records with multiple namespaces

Thanks for the input. Let's use - "name" : "attr_gender" Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Wed, Mar 2, 2016 at 11:31 AM, Susinda Perera

Re: [Dev] Issue in representing avro records with multiple namespaces

+1 to attr Awanthika Senarath Software Engineer, WSO2 Inc. Mobile: +94717681791 On Wed, Mar 2, 2016 at 11:31 AM, Susinda Perera wrote: > How about *attr* (lowercase) > > On Wed, Mar 2, 2016 at 11:29 AM, Sohani Weerasinghe > wrote: > >> I think it's better

Re: [Dev] Issue in representing avro records with multiple namespaces

How about *attr* (lowercase) On Wed, Mar 2, 2016 at 11:29 AM, Sohani Weerasinghe wrote: > I think it's better if we can use "ATR" instead of "ATT" > > Sohani Weerasinghe > Software Engineer > WSO2, Inc: http://wso2.com > > Mobile : +94 716439774 > Blog

Re: [Dev] Issue in representing avro records with multiple namespaces

I think it's better if we can use "ATR" instead of "ATT" Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Wed, Mar 2, 2016 at 11:25 AM, Sohani Weerasinghe

Re: [Dev] Issue in representing avro records with multiple namespaces

Hi All, When representing attributes in avro schema, according to [1] the suggested approach is to use @ as a prefix. Since avro name should start with [A-Za-z] and subsequently contain only [A-Za-z0-9_], shall we represent it as below (adding ATT as a prefix) "name" : "*ATT*_gender" [1]

Re: [Dev] Issue in representing avro records with multiple namespaces

​Please find the attached image which represents the prefix in the tree view Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Wed, Mar 2, 2016 at 7:45 AM,

Re: [Dev] Issue in representing avro records with multiple namespaces

Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Wed, Mar 2, 2016 at 6:28 AM, Jasintha Dasanayake wrote: > > > On Tue, Mar 1, 2016 at

Re: [Dev] Issue in representing avro records with multiple namespaces

On Tue, Mar 1, 2016 at 9:07 PM, Sohani Weerasinghe wrote: > Thanks Nuwan for the response. > > When generating the avro schema by adding elements to the tree view, user > can specify the namespace (xml namespace) with the prefix, so that when > generating the the avro schema we

Re: [Dev] Issue in representing avro records with multiple namespaces

Thanks Nuwan for the response. When generating the avro schema by adding elements to the tree view, user can specify the namespace (xml namespace) with the prefix, so that when generating the the avro schema we can map the namespace to doc and prefix to the namespace in avro. Thanks, Sohani

Re: [Dev] Issue in representing avro records with multiple namespaces

On Tue, Mar 1, 2016 at 7:34 PM, Sohani Weerasinghe wrote: > Hi All, > > If we consider an XML which has multiple namespaces as below , > > > http://www.w3.org/TR/html4/;> > Asian Coffee Table > 74 > 129 > > http://www.w3schools.com/furniture;> > African Coffee Table >

[Dev] Issue in representing avro records with multiple namespaces

Hi All, If we consider an XML which has multiple namespaces as below , http://www.w3.org/TR/html4/;> Asian Coffee Table 74 129 http://www.w3schools.com/furniture;> African Coffee Table 80 120 The avro schema should be as follows , { "type" : "record", "name" : "root",