+1

Zhichao Zhang


------------------ Original ------------------
From: "ravipesala [via Apache CarbonData Dev Mailing List 
archive]"<[email protected]>;
Date: Sat, Aug 31, 2019 05:11 PM
To: "????"<[email protected]>;

Subject: Re: Adapt to SparkSessionExtensions



        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 <[hidden email]> wrote: 

> 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 <[hidden email]> wrote: 
> > 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/java/org/apache/spark/sql/SparkSessionExtensions.html
> > 
> > Main Scope: 
> > 1. Compatible with Spark 2.3.2+ 
> > 2. Make Carbon Parser Pluggable 
> >                 a. Move to antlr4 based parser 
> > 3. Make Analyzer Rules Pluggable 
> > 4. Make Optimizer Rules Pluggable 
> > 5. Make Planning Strategies Pluggable 
> > 
> > We can have Sub jiras in order to cover all the scenarios due to this. 
> Please input your thoughts. 
> > 
> > Regards 
> > 
> 
--  
Thanks & Regards, 
Ravi 
                                
        
        
                        If you reply to this email, your message will be added 
to the discussion below:
                
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/Adapt-to-SparkSessionExtensions-tp83668p83947.html
      
                        To start a new topic under Apache CarbonData Dev 
Mailing List archive, email [email protected] 
                To unsubscribe from Apache CarbonData Dev Mailing List archive, 
click here.
                NAML

Reply via email to