Re: [DISCUSS] Plan for next two releases

["amareshwarisr ." <am...@gmail.com>]

Jaideep,

Are you still volunteering for 2.2 release? I think its time to plan for
2.2 release.

Thanks
Amareshwari

On Tue, Apr 28, 2015 at 6:00 PM, Jaideep Dhok <ja...@inmobi.com>
wrote:

> I can volunteer for the next release.
>
> Thanks,
> Jaideep
>
> On Tue, Apr 28, 2015 at 1:46 PM, amareshwarisr . <am...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > I have updated how to release wiki -
> >
> >
> https://cwiki.apache.org/confluence/display/LENS/How+to+release+Apapche+Lens
> > and release calendar
> > https://cwiki.apache.org/confluence/display/LENS/Release+Calendar.
> >
> > Your comments are welcome on the content. Put up any suggestions on
> making
> > the release process better as well on the wiki.
> >
> > I would encourage committers of Apache Lens to volunteer for next
> releases.
> > You can update your name against release version on the wiki, if you are
> > volunteering.
> >
> > Thanks
> > Amareshwari
> >
> > On Fri, Mar 27, 2015 at 12:26 PM, Jaideep Dhok <ja...@inmobi.com>
> > wrote:
> >
> > > Off the top of my head -
> > >
> > > 1. Consistency in logging - Choose one of SLF4J or Commons Logging and
> > use
> > > it everywhere.
> > > 2. Refactoring of LensClient API - right now this code is bit confusing
> > to
> > > use for a new developer because there are too many similar sounding
> > > classes.
> > > 3. Readability improvements - join resolvers and candidate table
> > resolvers
> > > need more comments.
> > > 4. Review use of static variables, see if we can get rid of them -
> > > LensServices comes to mind
> > > 5. Cleanup of test code, make tests run in parallel
> > > 6. Improve build time.
> > >
> > > Thanks,
> > > Jaideep
> > >
> > > On Fri, Mar 27, 2015 at 12:01 PM, Sharad Agarwal <sh...@apache.org>
> > > wrote:
> > >
> > > > Jaidepp, good idea. can you elaborate more on the code quality and be
> > > > specific on what items you are looking for?
> > > >
> > > > On Fri, Mar 27, 2015 at 11:50 AM, Jaideep Dhok <
> > jaideep.dhok@inmobi.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > > Before we start work on these items, may I propose a very short
> 'stop
> > > the
> > > > > world' cleanup period where we only focus on improving code
> quality?
> > > > >
> > > > > Thanks,
> > > > > Jaideep
> > > > >
> > > > > On Fri, Mar 27, 2015 at 11:39 AM, Srikanth Sundarrajan <
> > > > > sriksun@hotmail.com>
> > > > > wrote:
> > > > >
> > > > > > This looks a very good list of features for us to go after in the
> > > next
> > > > > two
> > > > > > releases.
> > > > > >
> > > > > > Regards
> > > > > > Srikanth Sundarrajan
> > > > > >
> > > > > > ----------------------------------------
> > > > > > > Date: Fri, 27 Mar 2015 11:37:49 +0530
> > > > > > > Subject: [DISCUSS] Plan for next two releases
> > > > > > > From: amareshwari@apache.org
> > > > > > > To: dev@lens.incubator.apache.org
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Starting this thread to discuss plan for what we should focus
> on
> > > next
> > > > > two
> > > > > > > releases. 2.1 can be called out with whatever went in as of now
> > and
> > > > > > > stabilize that. I will send out different discuss thread for
> 2.1
> > > > > release.
> > > > > > > This thread is mainly for 2.2 and 2.3.
> > > > > > >
> > > > > > > Here are some of the features/improvements, I'm putting out
> some
> > > > > > > significant features and improvements to start with :
> > > > > > >
> > > > > > > 1. Ability to load different instance of same driver class :
> > > LENS-123
> > > > > > > 2. Add scheduler service : LENS-124
> > > > > > > 3. Estimate query execution times : LENS-135
> > > > > > > 4. Query submission throttling : LENS-192
> > > > > > > 5. Add Druid driver : LENS-127
> > > > > > > 6. Improve query statistics and come up with indicative queries
> > for
> > > > > > > analysis : LENS-28 and LENS-193
> > > > > > > 7. Make the query language suitable to integrate with BI tools.
> > > > > > > 8. Allow multiple expressions for expression-column : LENS-122
> > > > > > > 9. Union across tables in cube rewriting : LENS-204
> > > > > > > 10. Support to query streaming data stores : LENS-251
> > > > > > > 11. Allow timed dimensions of cube to be non-partitioned
> columns
> > as
> > > > > well
> > > > > > > : LENS-198
> > > > > > >
> > > > > > > Please add to the above if you are looking for some features or
> > > > willing
> > > > > > to
> > > > > > > contribute. Let us discussion on the feature itself on the
> jira.
> > We
> > > > can
> > > > > > add
> > > > > > > the above to wiki. Will do that after a consensus.
> > > > > > >
> > > > > > > Thanks
> > > > > > > Amareshwari
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > -
> > > > > Jaideep Dhok
> > > > >
> > > > > --
> > > > > _____________________________________________________________
> > > > > The information contained in this communication is intended solely
> > for
> > > > the
> > > > > use of the individual or entity to whom it is addressed and others
> > > > > authorized to receive it. It may contain confidential or legally
> > > > privileged
> > > > > information. If you are not the intended recipient you are hereby
> > > > notified
> > > > > that any disclosure, copying, distribution or taking any action in
> > > > reliance
> > > > > on the contents of this information is strictly prohibited and may
> be
> > > > > unlawful. If you have received this communication in error, please
> > > notify
> > > > > us immediately by responding to this email and then delete it from
> > your
> > > > > system. The firm is neither liable for the proper and complete
> > > > transmission
> > > > > of the information contained in this communication nor for any
> delay
> > in
> > > > its
> > > > > receipt.
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > -
> > > Jaideep Dhok
> > >
> > > --
> > > _____________________________________________________________
> > > The information contained in this communication is intended solely for
> > the
> > > use of the individual or entity to whom it is addressed and others
> > > authorized to receive it. It may contain confidential or legally
> > privileged
> > > information. If you are not the intended recipient you are hereby
> > notified
> > > that any disclosure, copying, distribution or taking any action in
> > reliance
> > > on the contents of this information is strictly prohibited and may be
> > > unlawful. If you have received this communication in error, please
> notify
> > > us immediately by responding to this email and then delete it from your
> > > system. The firm is neither liable for the proper and complete
> > transmission
> > > of the information contained in this communication nor for any delay in
> > its
> > > receipt.
> > >
> >
>
>
>
> --
> -
> Jaideep Dhok
>
> --
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>