Thank you, Andrew, and Bet365 for hosting this event, and for shepherding Riak through these difficult times.
I will not be able to attend, but under enhancements, I would encourage the group to discuss the late enhancements to Riak/KV to support efficient bucket and key listing for sorted back ends. This work can be found on the develop and develop-2.2 branches of riak_kv; it was not formally shipped in any Basho production releases, but listing buckets has seen some testing (and the code changes are relatively small). Listing buckets in time proportional to the number of buckets (not the number of keys in the cluster), and keys in a bucket proportional to the number of keys in the bucket (not the number of keys in the cluster) seems like a laudable goal for which I am sure customers would find use cases. Key listing has always been an operation known to kill large clusters, and the advice has always been, "don't do that", despite its obvious utility. With these changes, that advice can be dropped for a subset of users. -Fred https://github.com/basho/riak_kv/pull/1634 <https://github.com/basho/riak_kv/pull/1634> https://github.com/basho/riak_kv/pull/1650 <https://github.com/basho/riak_kv/pull/1650> > On Sep 22, 2017, at 9:56 AM, andrew.de...@bet365.com wrote: > > Hi, > > We are beginning to plan out the two day workshop [1]. We are thinking the > first day will start with an introduction from Martin Davies, in which Martin > will detail current status and the asset list. > > After which we will get into project questions, such as: > > Which license? > The general consensus is Apache2. We need to complete the discussion as > HyperLogLog has been introduced which is GPL’d. Our thoughts are to replace > HLL. > > Baseline? > We have heard some discussion around where to baseline the codebase. The > concern is during the demise of Basho the correct level of diligence was not > applied to promotes meaning the code such as HLL has crept in. > > Governance? > How are we to manage the project going forward? Our feeling is we do not need > a formal body as being discussed in the slack group. We see the project going > forward as a simple repo into which likeminded developers agree and > contribute changes. Placing overbearing procedure and structure on what is > currently a small community will dissuade other from joining and contributing. > > Supporting infrastructure. > The Basho websites, github account, and mailing group are all included in the > deal. We are currently supporting the mailing list, and once the deal is > complete we will continue to support the Basho domains; restricting community > disruption. > > Roadmap > Below, in no particular order, are the items we wish to address internally. > If we can all share our lists we can come to an agreed community roadmap > between us. > > · Review / rationalisation of Basho JIRA tickets / git issues > > · Replication > o Address known issues (30+) to add stability > o Selective replication > o Persistent realtime queue > o Review of general approach > § In / out of band > § Snapshot vs deltas > > · General > o Address known issues (20+) to add stability > o Silent data loss bug in riak_kv > > · Enhancements > o G Sets > o Big Sets > o CRDT Maps > o Async read / write vnodes > o Split backend vnodes > o Head requests – don’t return body to co-ordinator > o Rudimentary indexing (leverage TS work) > > · Consolidation / feature cross population of KV,CS, and TS codebases > > · Erlang / OTP upgrade > > > At this point we want to keep the structure of the day loose to allow the > conversations to flow, our collective priorities to take precedence. > > The sessions will be live streamed, with details to follow. > > We will also man IRC / Slack for discourse. > > Food and refreshments will be provided throughout the two days. > > Hopefully this gives us something to discuss in the build up to the 12th Oct. > We’re looking for everyone’s input so we can hit the ground running. > > As a quick update on the status of the purchase. We have exchanged funds and > the court process continues. One clarifying point for anyone following the > court proceedings. The purchasing company is our technology arm, Hillside > Technology Limited, not the bet365 group. > > Thanks, > Andy. > > [1] > https://www.meetup.com/RIAK-Development-Roadmap-Workshop/events/243302656/ > <https://www.meetup.com/RIAK-Development-Roadmap-Workshop/events/243302656/> > > > Andrew Deane > Systems Development Manager - Middleware > Hillside (Technology) Limited > andrew.de...@bet365.com <mailto:andrew.de...@bet365.com> > bet365.com <http://bet365.com/> > > This email and any files transmitted with it are confidential and contain > information which may be privileged or confidential and are intended solely > to be for the use of the individual(s) or entity to which they are addressed. > If you are not the intended recipient be aware that any disclosure, copying, > distribution or use of the contents of this information is strictly > prohibited and may be illegal. If you have received this email in error, > please notify us by telephone or email immediately and delete it from your > system. Activity and use of our email system is monitored to secure its > effective operation and for other lawful business purposes. Communications > using this system will also be monitored and may be recorded to secure > effective operation and for other lawful business purposes. Internet emails > are not necessarily secure. We do not accept responsibility for changes made > to this message after it was sent. You are advised to scan this message for > viruses and we cannot accept liability for any loss or damage which may be > caused as a result of any computer virus. > > This email is sent by a bet365 group entity. The bet365 group includes the > following entities: Hillside (Shared Services) Limited (registration no. > 3958393), Hillside (Spain New Media) Plc (registration no. 07833226), bet365 > Group Limited (registration no. 4241161), Hillside (Technology) Limited > (registration no. 8273456), Hillside (Media Services) Limited (registration > no. 9171710), Hillside (Trader Services) Limited (registration no. 9171598) > each registered in England and Wales with a registered office address at > bet365 House, Media Way, Stoke-on-Trent, ST1 5SZ, United Kingdom; Hillside > (Gibraltar) Limited (registration no. 97927), Hillside (Sports) GP Limited > (registration no. 111829) and Hillside (Gaming) GP Limited (registered no. > 111830) each registered in Gibraltar with a registered office address at Unit > 1.1, First Floor, Waterport Place, 2 Europort Avenue, Gibraltar; Hillside (UK > Sports) LP (registration no. 117), Hillside (Sports) LP (registration no. > 118), Hillside (International Sports) LP (registration no. 119), Hillside > (Gaming) LP (registration no. 120) and Hillside (International Gaming) LP > (registration no. 121) each registered in Gibraltar with a principal place of > business at Unit 1.1, First Floor, Waterport Place, 2 Europort Avenue, > Gibraltar; Hillside España Leisure S.A (CIF no. A86340270) registered in > Spain with a registered office address at C/ Conde de Aranda nº20, 2º, 28001 > Madrid, Spain; Hillside (Australia New Media) Pty Limited (registration no. > 148 920 665) registered in Australia with a registered office address at > Level 4, 90 Arthur Street, North Sydney, NSW 2060, Australia; Hillside (New > Media Malta) Plc, (registration no c.66039) registered in Malta with a > registered office address at Office 1/2373, Level G, Quantum House, 75 Abate > Rigord Street, Ta’ Xbiex XBX 1120, Malta and Hillside (New Media Cyprus) > Limited, (registration no. HE 361612) registered in Cyprus with a registered > office address at Omrania Centre, 313, 28th October Avenue, 3105 Limassol, > Cyprus. Hillside (Shared Services) Limited, Hillside (Spain New Media) Plc > and Hillside (New Media Malta) Plc also have places of business at Unit 1.1, > First Floor, Waterport Place, 2 Europort Avenue, Gibraltar. For residents of > Greece, this email is sent on behalf of B2B Gaming Services (Malta) Limited > (registration number C41936) organised under the laws of Malta with a > registered office at Apartment 21, Suite 41, Charles Court, St. Luke's Road, > Pietà, Malta. _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com <mailto:riak-users@lists.basho.com> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > <http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com>
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
