+1, I agree with sujith.
We can have a seperate link in the website(example: *Breaking change*)
which can list all the behaviour changes that the new version is
introducing.
Regards,
Kunal Kapoor
On Wed, Sep 5, 2018 at 3:56 PM sujith chacko
wrote:
> +1,
> As this will improve our
+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
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
Hi Raghu
+1, all these optimizations are very good.
Regards
Liang
sraghunandan wrote
> Dear All,
>
> I wanted to propose some updates and changes to our current
> documentation,Please let me know your inputs and comments.
>
>
> 1.Split Our carbondata command into DDL and DML
>
> 2.Add
Dear All,
I wanted to propose some updates and changes to our current
documentation,Please let me know your inputs and comments.
1.Split Our carbondata command into DDL and DML
2.Add Presto and Hive integration along with Spark into quick start
3.Add a master reference manual which lists all
