Hi Ajith,
1. Now if the config includes spark extensions can we configure the carbon
store path and metastoreDB path while creating spark session instance
2. Impact on the existing carbonsession user for spark 2.3.x user mentions that
there will be "no profiler and no refresh across driver". C
+1
Zhichao Zhang
-- Original --
From: "ravipesala [via Apache CarbonData Dev Mailing List
archive]";
Date: Sat, Aug 31, 2019 05:11 PM
To: ""<441586...@qq.com>;
Subject: Re: Adapt to SparkSessionExtensions
Hi,
I thi
+1
Regards
Kumar Vishal
On Sat, 31 Aug 2019 at 14:37, Ravindra Pesala wrote:
> Hi,
>
> I think it is better to work on the master branch instead of 2.0 branch. It
> will avoid the rebase cost and unnecessary confusion. it is better to go
> with proper version quality.
>
> Regards,
> Ravindra.
>
Hi,
I think it is better to work on the master branch instead of 2.0 branch. It
will avoid the rebase cost and unnecessary confusion. it is better to go
with proper version quality.
Regards,
Ravindra.
On Mon, 26 Aug 2019 at 8:13 PM, Jacky Li wrote:
> I have created branch-2.0, let's work on th
+1
regards
David QiangCai
I have created branch-2.0, let's work on this feature in this branch.
Regards,
Jacky
On 2019/08/22 04:58:53, Ajith shetty wrote:
> Hi Community
>
> From https://issues.apache.org/jira/browse/SPARK-18127 Spark provides
> SparkSessionExtensions in order to extended capabilities of spark. Carbon
+1
And since we are starting this refactory for CarbonData 2.0 which is a major
version upgrade, I suggest to consider optimize following features:
1. make global dictionary obsolete so that planning phase is cleaner. After
spark tungsten project, actually the benefit get from global dictionary
Hi Community
>From https://issues.apache.org/jira/browse/SPARK-18127 Spark provides
>SparkSessionExtensions in order to extended capabilities of spark. Carbon can
>use this in order to avoid the tight coupling due to CarbonSession in spark
>environment.
https://spark.apache.org/docs/2.4.3/api/j
