+1, As this will improve our documentation quality, just have 1 suggestions, do we need to have a migration guide also in carbon or a section which basically says any behaviour changes while migrating the carbon versions. This will be very handy when we release our major versions.
Fo Example if any behaviour changes in bad records handling across version or changes in behaviour of particular data type data like decimal precision/scale handling etc. Regards, Sujith On Wed, 5 Sep 2018 at 7:39 AM, xuchuanyin <xuchuan...@hust.edu.cn> wrote: > I think even we split the carbondata command into DDL and DML, it is still > too large for one document. > > For example, there are many TBLProperties for creating table in DDL. Some > descriptions of the TBLProperties is long and now we do not have TOC for > them. It's difficult to locate one property in the doc. > > Besides, some parameters can be specified in system configuration, > TBLProperties, LoadOptions level at the same time. Where should we describe > this parameter? > > > > -- > Sent from: > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ >
