Made changes in UPDAT/DELETE section as suggested and added compaction hyperlink in DML section of language manual. Other information is either already present in other documents or not necessary.
> Documentation Issue in Github Docs Link
https://github.com/apache/carbondata/tree/master/docs> ----------------------------------------------------------------------------------------------
>
> Key: CARBONDATA-3903
> URL:
https://issues.apache.org/jira/browse/CARBONDATA-3903> Project: CarbonData
> Issue Type: Bug
> Components: docs
> Affects Versions: 2.0.1
> Environment:
https://github.com/apache/carbondata/tree/master/docs> Reporter: PURUJIT CHAUGULE
> Priority: Minor
>
> dml-of-carbondata.md
> LOAD DATA:
> * Mention Each Load is considered as a Segment.
> * Give all possible options for SORT_SCOPE like GLOBAL_SORT/LOCAL_SORT/NO_SORT (with explanation of difference between each type).
> * Add Example Of complete Load query with/without use of OPTIONS.
> INSERT DATA:
> * Mention each insert is a Segment.
> LOAD Using Static/Dynamic Partitioning:
> * Can give a hyperlink to Static/Dynamic partitioning.
> UPDATE/DELETE:
> * Mention about delta files concept in update and delete.
> DELETE:
> * Add example for deletion of all records from a table (delete from tablename).
> COMPACTION:
> * Can mention Minor compaction of two types Auto and Manual( carbon.auto.load.merge =true/false), and that if carbon.auto.load.merge=false, trigger should be done manually.
> * Hyperlink to Configurable properties of Compaction.
> * Mention that compacted segments do not get cleaned automatically and should be triggered manually using clean files.
>
> flink-integration-guide.md
> * Mention what are stages, how is it used.
> * Process of insertion, deletion of stages in carbontable. (How is it stored in carbontable).
>
> language-manual.md
> * Mention Compaction Hyperlink in DML section.
>
> spatial-index-guide.md
> * Mention the TBLPROPERTIES supported / not supported for Geo table.
> * Mention Spatial Index does not make a new column.
> * CTAS from one geo table to another does not create another Geo table can be mentioned.
> * Mention that a certain combination of Spatial Index table properties need to be added in create table, without which a geo table does not get created.
> * Mention that we cannot alter columns (change datatype, change name, drop) mentioned in spatial_index.
>
Locked
