I'm working on https://issues.apache.org/jira/browse/DRILL-6877. Will try to complete by today.
Thank you, Jyothsna On Mon, Dec 3, 2018 at 2:42 AM Arina Yelchiyeva <arina.yelchiy...@gmail.com> wrote: > Looks like this is a release blocker: > https://issues.apache.org/jira/browse/DRILL-6877 > This is a regression after DRILL-6039. > > Kind regards, > Arina > > On Thu, Nov 29, 2018 at 6:24 PM Vitalii Diravka <vita...@apache.org> > wrote: > > > Hello drillers! > > > > I am going to merge the changes for 5 PR with ready-to-commit label > > (DRILL-6867, DRILL-6866, DRILL-6863, DRILL-6792, DRILL-6039) > > and then to start the release process. > > Please do not merge any new commits to master branch. > > > > > > Kind regards > > Vitalii > > > > > > On Tue, Nov 27, 2018 at 5:40 PM Vitalii Diravka <vita...@apache.org> > > wrote: > > > > > Hi all! > > > Thanks for updating tickets. > > > > > > There are couple of tickets, which are almost done and would be nice to > > > include them to 1.15 release: > > > Can be merged: > > > DRILL-6864 ben-zvi Root POM: Update the git-commit-id plugin > > > DRILL-6039 vdonapati drillbit.sh graceful_stop does not wait for > > > fragments to complete before stopping the drillbitAlmost ready to > commit: > > > DRILL-6867 le.louch WebUI Query editor cursor position > > > DRILL-6792 weijie Find the right probe side fragment to any storage > > plugin > > > DRILL-6806 timothyfarkas Start moving code for handling a partition in > > > HashAgg into a separate class > > > Also I am planning to include DRILL-6562: Upgrade to SqlLine 1.6.0 and > my > > > work - DRILL-6562: Plugin Management improvements. > > > I suppose these tickets will be addressed in the next few days, then I > > > will start release process. > > > > > > Kind regards > > > Vitalii > > > > > > > > > On Mon, Nov 26, 2018 at 7:50 PM Vitalii Diravka <vita...@apache.org> > > > wrote: > > > > > >> Hi all! > > >> > > >> I found the issue DRILL-6828 [1], which is introduced in DRILL-6381. I > > >> think it is an important one, since the issue is a degradation and it > > >> blocks working with HashPartitionSender exchange operator. > > >> Boaz, since you are assigned to the jira, could you please take a > look? > > >> > > >> Charles, your "REST metadata" work is merged. Regarding "Syslog > plugin" > > I > > >> will do review, but as usual process. I mean it should not block the > > >> release. > > >> > > >> Team, these are tickets, which should be updated to make the release > in > > >> time. Please change the release version to 1.16, if it is not a > blocker > > and > > >> requires additional work. > > >> Issue key Assignee Summary > > >> DRILL-6845 ben-zvi Eliminate duplicates for Semi Hash Join > > >> DRILL-6864 ben-zvi Root POM: Update the git-commit-id plugin > > >> DRILL-6867 le.louch WebUI Query editor cursor position > > >> DRILL-6849 weijie Runtime filter queries with nested broadcast returns > > >> wrong results > > >> DRILL-6838 weijie Query with Runtime Filter fails with > > >> IllegalStateException: Memory was leaked by query > > >> DRILL-6792 weijie Find the right probe side fragment to any storage > > >> plugin > > >> DRILL-6791 Paul.Rogers Merge scan projection framework into master > > >> DRILL-6039 vdonapati drillbit.sh graceful_stop does not wait for > > >> fragments to complete before stopping the drillbit > > >> DRILL-6806 timothyfarkas Start moving code for handling a partition in > > >> HashAgg into a separate class > > >> DRILL-6543 ben-zvi Option for memory mgmt: Reserve allowance for > > >> non-buffered > > >> DRILL-6863 KazydubB Drop table is not working if path within workspace > > >> starts with '/' > > >> DRILL-6253 timothyfarkas HashAgg Unit Testing And Refactoring > > >> DRILL-6032 timothyfarkas Use RecordBatchSizer to estimate size of > > >> columns in HashAgg > > >> DRILL-6623 karthikm Drill encounters exception > > >> IndexOutOfBoundsException: writerIndex: -8373248 (expected: > > readerIndex(0) > > >> <= writerIndex <= capacity(32768)) > > >> DRILL-6245 vdonapati Clicking on anything redirects to main login page > > >> [1] > > >> > > > https://issues.apache.org/jira/browse/DRILL-6828?focusedCommentId=16699152&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16699152 > > >> > > >> > > >> Kind regards > > >> Vitalii > > >> > > >> > > >> On Tue, Nov 20, 2018 at 3:06 PM Charles Givre <cgi...@gmail.com> > wrote: > > >> > > >>> Hi @Vitalii > > >>> Are you sure? The metadata commit is really pretty minor now that I > > >>> cleaned it up. If nobody can review the Syslog format plugin until > the > > >>> next version, that’s fine, but I don’t think it should be a big deal > to > > >>> review either. > > >>> Best, > > >>> — C > > >>> > > >>> > On Nov 20, 2018, at 05:20, Vitalii Diravka <vita...@apache.org> > > wrote: > > >>> > > > >>> > @Charles Your changes require some time to pass review, it is > better > > to > > >>> > consider them to the next release. > > >>> > All other mentioned issues are resolved. > > >>> > > > >>> > Team, please verify the tickets which you are responsible for and > > >>> update > > >>> > them accordingly [1]. > > >>> > If there are no blockers we can consider to include one more > > >>> batch-commit > > >>> > to the 1.15.0 Drill release. > > >>> > Therefore 27.11 can be the final cut-off date. > > >>> > > > >>> > [1] > > >>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=185 > > >>> > > > >>> > Kind regards > > >>> > Vitalii > > >>> > > > >>> > > > >>> > On Wed, Nov 7, 2018 at 2:24 AM Vitalii Diravka <vita...@apache.org > > > > >>> wrote: > > >>> > > > >>> >> @Charles I think we can include it into 1.15.0 release, it also > will > > >>> >> depend on the review process. > > >>> >> It looks like it is DRILL-6582 Jira ticket. I have updated "Fix > > >>> Version/s" > > >>> >> for it. > > >>> >> > > >>> >> @Khurram Vova and me posted the info in the ticket. Please try to > > use > > >>> *PreparedStatement.executeQuery(). > > >>> >> *If it works, please close the jira. > > >>> >> > > >>> >> @Karthik For sure, it should be included to 1.15.0 Drill release. > > >>> >> > > >>> >> @Gautam You are right, it will be good to include this issue into > > >>> current > > >>> >> release, > > >>> >> since Drill SI based on MapR-DB data source and it should work > > >>> properly. > > >>> >> > > >>> >> Therefore we have more than one week to reduce the number of > tickets > > >>> from > > >>> >> [1] > > >>> >> > > >>> >> [1] > > >>> >> > > >>> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20DRILL%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Reviewable%2C%20Accepted)%20AND%20fixVersion%20%3D%201.15.0%20AND%20(component%20!%3D%20Documentation%20OR%20component%20is%20null)%20%20AND%20(labels%20!%3D%20ready-to-commit%20OR%20labels%20is%20null)%20ORDER%20BY%20status%20DESC%2C%20updated%20DESC > > >>> >> > > >>> >> Kind regards > > >>> >> Vitalii > > >>> >> > > >>> >> > > >>> >> On Wed, Nov 7, 2018 at 3:52 AM Gautam Parai <gpa...@mapr.com> > > wrote: > > >>> >> > > >>> >>> Hi Vitalii, > > >>> >>> > > >>> >>> Thanks for volunteering to be the release manager! > > >>> >>> > > >>> >>> I am currently working on DRILL-6770( > > >>> >>> https://issues.apache.org/jira/browse/DRILL-6770) which is > > >>> upgrading the > > >>> >>> MapR/OJAI versions. We are running into some wrong results issues > > >>> and I am > > >>> >>> actively working on it. > > >>> >>> > > >>> >>> I think we should definitely try to get it in this release. I > > think I > > >>> >>> should be done by the end of next week (11/16). > > >>> >>> > > >>> >>> Thanks, > > >>> >>> Gautam > > >>> >>> > > >>> >>> On Tue, Nov 6, 2018 at 12:28 PM Karthikeyan Manivannan < > > >>> >>> kmanivan...@mapr.com> > > >>> >>> wrote: > > >>> >>> > > >>> >>>> We should try to get "DRILL-5671: Set secure ACLs (Access > Control > > >>> List) > > >>> >>> for > > >>> >>>> Drill ZK nodes in a secure cluster" into 1.15. > > >>> >>>> Already +1ed by a committer but waiting for a +1 from another > > >>> committer > > >>> >>> who > > >>> >>>> had also participated in the review. > > >>> >>>> > > >>> >>>> On Tue, Nov 6, 2018 at 9:46 AM Vitalii Diravka < > > vita...@apache.org> > > >>> >>> wrote: > > >>> >>>> > > >>> >>>>> Hi Drillers, > > >>> >>>>> > > >>> >>>>> It's been 3 months since the last release and it is time to do > > the > > >>> >>> next > > >>> >>>>> one. > > >>> >>>>> > > >>> >>>>> I'll volunteer to manage the release :) > > >>> >>>>> > > >>> >>>>> There are 32 open tickets that are still intended to be > included > > in > > >>> >>>> 1.15.0 > > >>> >>>>> release [1]. > > >>> >>>>> What do you guys think which tickets do we want to include and > > what > > >>> >>> time > > >>> >>>>> will it take? > > >>> >>>>> If there are any other issues on which work is in progress, > that > > >>> you > > >>> >>> feel > > >>> >>>>> we *must* include in the release, please post in reply to this > > >>> thread. > > >>> >>>>> > > >>> >>>>> Based on your input we'll define release cut off date. > > >>> >>>>> > > >>> >>>>> [1] > > >>> >>>>> > > >>> >>>>> > > >>> >>>> > > >>> >>> > > >>> > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_issues_-3Fjql-3Dproject-2520-253D-2520DRILL-2520AND-2520status-2520in-2520-28Open-252C-2520-2522In-2520Progress-2522-252C-2520Reopened-252C-2520Reviewable-252C-2520Accepted-29-2520AND-2520fixVersion-2520-253D-25201.15.0-2520AND-2520-28component-2520-21-253D-2520Documentation-2520OR-2520component-2520is-2520null-29-2520-2520AND-2520-28labels-2520-21-253D-2520ready-2Dto-2Dcommit-2520OR-2520labels-2520is-2520null-29-2520ORDER-2520BY-2520status-2520DESC-252C-2520updated-2520DESC&d=DwIFaQ&c=cskdkSMqhcnjZxdQVpwTXg&r=HlugibuI4IVjs-VMnFvNTcaBtEaDDqE4Ya96cugWqJ8&m=akL-98gphoiivbhujdlv6Tf87UzIw9APJX71G9BDSFw&s=A8aoDFlrsbwTNj6NZPNVHYYMIyqVmfKEeDSM0Jb_ZZc&e= > > >>> >>>>> > > >>> >>>>> Kind regards > > >>> >>>>> Vitalii > > >>> >>>>> > > >>> >>>> > > >>> >>> > > >>> >> > > >>> > > >>> > > >
