Hi all,

Please find below notes from the meeting held regarding Visual DataMapper
on 24th April 2014.

*Participants: *Sanjiva, Isabelle, Srinath, Kasun, Jasintha, AsankaS,
Susinda, Lali, Sohani and me.

*Points discussed:*

*Visual Schema builder*

   - Visual schema builder contains avro terminology like Record, Records
   list, Field etc. These should be replaced by generic schema terminology
   like Type, Attribute/Property etc.
   - A newly added element gets a default name and to change this, user has
   to navigate to properties view. This can be simplified by enabling editing
   on the element itself.
   - Unnecessary properties (value and level) have to be removed from the
   properties view.
   - Currently, element type options are directly coming from avro
   specification. This list has to be cleaned up by removing options which are
   not used frequently (ENUM, UNION etc.).

*Data mapping editor*

   - There should be a facility to export updated avro schema back to the
   file system.
   - Move all defined types to a type repository.
   - A new option can be introduced to import a sample data set (JSON, XML
   etc.) to the editor and generate the respective avro schema. This will be
   done in the next demo for a simple json input.

*Data mapping engine*

   - Performance and load testing have to be done on top of the current
   engine.

Thanks,

-- 
*Gayan Kaushalya Yalpathwala*
 Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 71 8682704 <http://asia14.wso2con.com/>

<http://asia14.wso2con.com/>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to