This is a summary according to my understanding of the discussion so far: BOOKKEEPER-575: Bookie SSL support (umbrella jira) BOOKKEEPER-XXX: Provide support for bookie authentication BOOKKEEPER-390: Provide support for zookeeper authentication BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10 characters max, which fundamentally limits them at 9 billion BOOKKEEPER-590: Another Scan-And-Compare GC Implementation BOOKKEEPER-592: allow application to recommend ledger data locality (ready to go) BOOKKEEPER-432: Improve performance of entry log range read per ledger entries BOOKKEEPER-220: Managed ledger (optional, but nice to have)
Are these the core jiras we need to resolve for 4.3.0? -Flavio -----Original Message----- From: Ivan Kelly [mailto:[email protected]] Sent: 22 May 2013 14:43 To: [email protected] Subject: Re: [DISCUSS] Release 4.3.0 > > [fpj] Is there a jira for the SASL work? Do happen to know all jiras > related to security we need to address? There's no JIRA for sasl or auth yet. SSL is https://issues.apache.org/jira/browse/BOOKKEEPER-575 > > > - skiplist based ledger storage and other improvements on bookie server > > > side (there was already patches in 4.2.0 release) > > This is pretty close to ready. It needs some testing though. I'll > > try to > get a set of tests carved > > out by the end of the week. For 4.3.0 this will be disabled by > > default in > any case. > > [fpj] What's the jira or umbrella jira for this one? BOOKKEEPER-432 -Ivan
