Hi Indumathi, Design document covers all aspects of the implementation which is good except few minor points are missing i think like, It will be better if we can list down the constraints in our implementations if any, like a)Can we use map data type columns as partition key columns? b) It will be clear if you can mention all the data types which is supported, like do we support all primitive types especially timestanp since its one of the important type of key for map data type e.g. you can store the events corresponding to a time periods. c) Any restrictions in the level of nesting? eg 50 or 100
Thanks, Sujith On Mon, 20 Aug 2018 at 4:24 PM, Indhumathi <indhumathi...@gmail.com> wrote: > Hi all, > > Please find the Attached MAP-DataType support Design document. Please let > me > know for any further clarification on design document. > Any further suggestions/improvements are welcomed. > > MAP_DATA-TYPE_SUPPORT.pdf > < > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/file/t341/MAP_DATA-TYPE_SUPPORT.pdf> > > > Please find the link for design document. > > https://docs.google.com/document/d/1HHe2fdkIh3Jyz1y3494_2kGRSc4muTWuilAmwg5lpVw/edit?usp=sharing > < > https://docs.google.com/document/d/1HHe2fdkIh3Jyz1y3494_2kGRSc4muTWuilAmwg5lpVw/edit?usp=sharing> > > > Regards > Indhumathi M > > > > -- > Sent from: > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ >
