Jaideep, can you create specific jiras for the issues you are talking about? May be we can try and pull them into 2.1 itself.
Thanks Amareshwari On Fri, Mar 27, 2015 at 11:50 AM, Jaideep Dhok <[email protected]> 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 < > [email protected]> > 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: [email protected] > > > To: [email protected] > > > > > > 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. >
