Hi

Thanks you participated in discussion.

Currently, CarbonData has been formally deployed by many users.

Just like i mentioned in the previous post, take 1.0.0,it would be helpful
to reduce maintenance cost through 
distinguishing the major different version.

Regards
Liang

cenyuhai wrote
> -1
> I think 1.0.0 should be a production-ready version, when we think carbon
> is ready, we can change it to 1.0.0.
> 
> 
> Regards
> yuhai
> 
> 
> 
> 
> ------------------ 原始邮件 ------------------
> 发件人: "sujith chacko";<

> sujithchacko.2010@

> >;
> 发送时间: 2016年11月25日(星期五) 下午5:30
> 收件人: "dev"<

> dev@.apache

> >; 
> 
> 主题: Re: CarbonData propose major version number increment for nextversion
> (to 1.0.0)
> 
> 
> 
> +1
> 
> Thanks,
> Sujith
> 
> On Nov 24, 2016 10:37 PM, "manish gupta" <

> tomanishgupta18@

> > wrote:
> 
>> +1
>>
>> Regards
>> Manish Gupta
>>
>> On Thu, Nov 24, 2016 at 7:30 PM, Kumar Vishal <

> kumarvishal1802@

> >
>> wrote:
>>
>> > +1
>> >
>> > -Regards
>> > Kumar Vishal
>> >
>> > On Thu, Nov 24, 2016 at 2:41 PM, Raghunandan S <
>> > 

> carbondatacontributions@

>> wrote:
>> >
>> > > +1
>> > > On Thu, 24 Nov 2016 at 2:30 PM, Liang Chen &lt;

> chenliang6136@

> &gt;
>> > > wrote:
>> > >
>> > > > Hi
>> > > >
>> > > > Ya, good proposal.
>> > > > CarbonData 0.x version integrate with spark 1.x,  and the load data
>> > > > solution
>> > > > of 0.x version is using kettle.
>> > > > CarbonData 1.x version integrate with spark 2.x, the load data
>> solution
>> > > of
>> > > > 1.x version will not use kettle .
>> > > >
>> > > > That would be helpful to reduce maintenance cost through
>> distinguishing
>> > > the
>> > > > major different version.
>> > > >
>> > > > +1 for the proposal.
>> > > >
>> > > > Regards
>> > > > Liang
>> > > >
>> > > >
>> > > > Venkata Gollamudi wrote
>> > > > > Hi All,
>> > > > >
>> > > > > CarbonData 0.2.0 has been a good work and stable release with lot
>> of
>> > > > > defects fixed and with number of performance improvements.
>> > > > >
>> > > > https://issues.apache.org/jira/browse/CARBONDATA-320?
>> > jql=project%20%3D%
>> > >
>> 20CARBONDATA%20AND%20fixVersion%20%3D%200.2.0-incubating%20ORDER%20BY%
>> > > 20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>> > > > >
>> > > > > Next version has many major and new value added features are
>> planned,
>> > > > > taking CarbonData capability to next level.
>> > > > > Like
>> > > > > - IUD(Insert-Update-Delete) support,
>> > > > > - complete rewrite of data load flow with out Kettle,
>> > > > > - Spark 2.x support,
>> > > > > - Standardize CarbonInputFormat and CarbonOutputFormat,
>> > > > > - alluxio(tachyon) file system support,
>> > > > > - Carbon thrift format optimization for fast query,
>> > > > > - Data loading performance improvement and In memory off heap
>> > sorting,
>> > > > > - Query performance improvement using off heap,
>> > > > > - Support Vectorized batch reader.
>> > > > >
>> > > > >
>> > > > https://issues.apache.org/jira/browse/CARBONDATA-301?
>> > jql=project%20%3D%
>> > >
>> 20CARBONDATA%20AND%20fixVersion%20%3D%200.3.0-incubating%20ORDER%20BY%
>> > > 20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>> > > > >
>> > > > > I think it makes sense to change CarbonData Major version in next
>> > > version
>> > > > > to 1.0.0.
>> > > > > Please comment and vote on this.
>> > > > >
>> > > > > Thanks,
>> > > > > Ramana
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > View this message in context:
>> > > > http://apache-carbondata-mailing-list-archive.1130556.
>> > > n5.nabble.com/CarbonData-propose-major-version-number-
>> > > increment-for-next-version-to-1-0-0-tp3131p3157.html
>> > > > Sent from the Apache CarbonData Mailing List archive mailing list
>> > archive
>> > > > at Nabble.com.
>> > > >
>> > >
>> >
>>





--
View this message in context: 
http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/CarbonData-propose-major-version-number-increment-for-next-version-to-1-0-0-tp3131p3199.html
Sent from the Apache CarbonData Mailing List archive mailing list archive at 
Nabble.com.

Reply via email to