Hi Shivram, This framework is not ORC oriented, it does not care any specific file system or format in fact per my understanding.
And yes, I have required that its design proposal should be available in community for comment before delivery. Best, Yi On Thu, Aug 3, 2017 at 3:53 AM, Shivram Mani <[email protected]> wrote: > Yi, for the pluggable storage framework to be merged to master we need to > have a more detailed proposal talking about design/implementation etc. It > has been more than a year since the first ORC related draft was first > published for the pluggable framework. August timeline seems very unlikely. > > On Tue, Jul 25, 2017 at 5:45 AM, Yi JIN <[email protected]> wrote: > > > Thank Lili and Radar for your comment. > > > > Following Vineet's comment, I have changed timeline to have branch cut > > scheduled at 1st Sept. > > > > And TDE will be involved in this release per your requests. Please Radar > > help plan TDE delivery in Aug. > > > > Currently, pluggable external storage supporting framework per my > > understanding is under construction at a wrap-up phase, it will be > smoothly > > delivered into repo in Aug as well when it has enough test cases > verified. > > > > Best, > > Yi > > > > On Tue, Jul 25, 2017 at 6:39 PM, Radar Lei <[email protected]> wrote: > > > > > Thanks Yi. > > > > > > Cut release branch at early/middle September looks fine. > > > > > > I would suggest we can add TDE support in the release plan too. > > > > > > Regards, > > > Radar > > > > > > On Tue, Jul 25, 2017 at 2:37 PM, Lili Ma <[email protected]> wrote: > > > > > > > Hi Yi, > > > > > > > > What's the status of pluggable external storage? > > > > > > > > Also, I wonder whether we can add TDE in next release. > > > > > > > > Thanks > > > > Lili > > > > > > > > 2017-07-25 13:25 GMT+08:00 Vineet Goel <[email protected]>: > > > > > > > > > Sounds good to me, Yi. > > > > > If there are any other suggestions from other members, those are > > > welcome > > > > > too. > > > > > > > > > > Thank you. > > > > > > > > > > > > > > > > > > > > On Thu, Jul 20, 2017 at 6:14 PM Yi JIN <[email protected]> > > wrote: > > > > > > > > > > > Hi Vineet, > > > > > > > > > > > > Thank you for your comment, I will add timeline on release page > as > > > part > > > > > of > > > > > > the plan. > > > > > > > > > > > > Basically, I expect by 30th Oct., we can have tar balls available > > for > > > > > > downloading, and before that I reserve about 1.5 month for voting > > > > > progress > > > > > > according to previous experiences. So basically, I think we can > cut > > > > > branch > > > > > > for new release at mid Sept. So that means we have no more than 2 > > > > months > > > > > > for fixing and new feature delivery. As delivering pluggable > > external > > > > > > storage requires some time. If necessary, I think it is ok to > move > > > > target > > > > > > date 2 weeks earlier. Does this rough time schedule make sense? > > > What's > > > > > your > > > > > > opinion? > > > > > > > > > > > > I will add Umbrella JIRAS on that page as well. > > > > > > > > > > > > Best, > > > > > > Yi Jin (yjin) > > > > > > > > > > > > On Thu, Jul 20, 2017 at 3:52 PM, Vineet Goel <[email protected] > > > > > > wrote: > > > > > > > > > > > > > Hi Yi, > > > > > > > > > > > > > > Thank you for the initiative. I have some feedback that we can > > > > discuss > > > > > > here > > > > > > > and collect further input on. > > > > > > > > > > > > > > a) Putting a timeline on releases (such as October 31st here) > may > > > > have > > > > > > some > > > > > > > downsides to the process. My thoughts are that more frequent > > > releases > > > > > > give > > > > > > > users access to features and fixes faster, from a stable > branch. > > > > > Release > > > > > > > momentum is good to have in any project. For instance, master > > > branch > > > > is > > > > > > > already 75+ commits ahead of 2.2.0.0-incubating, since that > > branch > > > > was > > > > > > cut > > > > > > > a a couple of months back. > > > > > > > > > > > > > > b) Also, it may help to add Umbrella JIRAs on that page, > > associated > > > > to > > > > > > the > > > > > > > new features. If certain features are too large to finish in a > > > given > > > > > > > release, they can always ride the next release vehicle. > > > > > > > > > > > > > > It would be good to hear thoughts from others. > > > > > > > > > > > > > > Thanks! > > > > > > > Vineet > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Jul 19, 2017 at 6:15 PM Yi JIN <[email protected]> > wrote: > > > > > > > > > > > > > > > Hi Apache HAWQ community, > > > > > > > > > > > > > > > > Thank you guys for your trust, I drafted one release plan for > > > next > > > > > > > version > > > > > > > > 2.3.0.0 that has been update in wiki as below. Please feel > free > > > to > > > > > > > comment > > > > > > > > and any input is welcome. Thank you again. > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/HAWQ/ > > > > > Apache+HAWQ+2.3.0.0- > > > > > > > incubating+Release > > > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > Yi Jin (yjin) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > shivram mani >
