Hi all:
Got it, thanks for your suggestions, I will implement this and raise a pr.
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Yes, I agree with Liang. We no need to consider showing sql in describe
table in case of CTAS.
Regards
Ravindra
On Tue, 21 Aug 2018 at 20:47, Raghunandan S <
carbondatacontributi...@gmail.com> wrote:
> Hi,
> In opinion it is not required to show the original select sql. Also is
> there a way to
Hi,
Current Carbondata has deep integration with Spark to provide optimizations
in performance and also supports features like compaction, IUD, data maps
and metadata management etc. This type of integration forces user to use
CarbonSession instance to use carbon even for read and write operations
Hi,
In opinion it is not required to show the original select sql. Also is
there a way to get it? I don't think it can be got.
Regards
Raghu
On Tue, 21 Aug 2018, 8:02 pm Liang Chen, wrote:
> Hi
>
> 1. Agree with likun's comments(4 points) :
>
> 2. About 'select sql' for CTAS , you can leave it
Hi
1. Agree with likun's comments(4 points) :
2. About 'select sql' for CTAS , you can leave it. we can consider it later.
Regards
Liang
Jacky Li wrote
> Hi ZZC,
>
> I have checked the doc in CARBONDATA-2595. I have following comments:
> 1. In the Table Basic Information section, it is better
Hi ZZC,
I have checked the doc in CARBONDATA-2595. I have following comments:
1. In the Table Basic Information section, it is better to print the Table Path
instead of "CARBON Store Path”
2. For the Table Data Size and Index Size, can you format the output in GB,
MB, KB, etc
3. For the Last Up
