I think that was intent but ran out of time. There were 2 approaches to this, one being dumping the Metric's into a virtual table, and another to have specialized views (like nodetool). The later is started in CASSANDRA-14670 <https://issues.apache.org/jira/browse/CASSANDRA-14670> and still waiting on a reviewer, and the former had some disagreements since people did not want to couple our internal metric implementation to the view operators would see. Ultimately though there was only so much time to create virtual tables before the 4.0 freeze from when the system_views was added and virtual tables are considered new features so not applicable for being added during freeze (was my understanding at least). There are a few other virtual tables waiting for reviewers if there are any volunteers too and I know I personally have a few in queue for whenever trunk is accepting new things again.
Chris On Tue, May 28, 2019 at 2:42 PM Kyle Samson <kysam...@tripadvisor.com> wrote: > Hey all, > > Thought I’d chime in here as one of the people surprised that virtual > tables for table stats weren’t being included in 4.0, especially given that > QoL for administrators is one of the 4.0 promises. > > -Kyle Samson > > On 2019/05/28 16:39:59, Jon Haddad <j...@jonhaddad.com> wrote: > > Sept is a pretty long ways off. I think the ideal case is we can > announce> > > 4.0 release at the summit. I'm not putting this as a "do or die" date, > and> > > I don't think we need to announce it or make promises. Sticking with > "when> > > it's ready" is the right approach, but we need a target, and this is imo > a> > > good one.> > > > > This date also gives us a pretty good runway. We could cut our first> > > alphas in mid June / early July, betas in August and release in Sept.> > > There's a ton of work going into testing 4.0 already.> > > Landing CASSANDRA-15066 will put us in a pretty good spot. We've > developed> > > tooling at TLP that will make it a lot easier to spin up dev clusters > in> > > AWS as well as stress test them. I've written about this a few times > in> > > the past, and I'll have a few blog posts coming up that will help show > this> > > in more details.> > > > > There's some other quality of life things we should try to hammer out> > > before then. Updating our default JVM settings would be nice, for> > > example. Improving documentation (the data modeling section in> > > particular), fixing the dynamic snitch issues [1], and some improvements > to> > > virtual tables like exposing the sstable metadata [2], and exposing > table> > > statistics [3] come to mind. The dynamic snitch improvement will help> > > performance in a big way, and the virtual tables will go a long way to> > > helping with quality of life. I showed a few folks virtual tables at > the> > > Accelerate conference last week and the missing table statistics was a > big> > > shock. If we can get them in, it'll be a big help to operators.> > > > > [1] https://issues.apache.org/jira/browse/CASSANDRA-14459> > > [2] https://issues.apache.org/jira/browse/CASSANDRA-14630> > > [3] https://issues.apache.org/jira/browse/CASSANDRA-14572> > > > > > > > > > > On Mon, May 27, 2019 at 2:36 PM Nate McCall <zz...@gmail.com> wrote:> > > > > > Hi Sumanth,> > > > Thank you so much for taking the time to put this together.> > > >> > > > Cheers,> > > > -Nate> > > >> > > > On Tue, May 28, 2019 at 3:27 AM Sumanth Pasupuleti <> > > > sumanth.pasupuleti...@gmail.com> wrote:> > > >> > > > > I have taken an initial stab at documenting release types and exit> > > > criteria> > > > > in a google doc, to get us started, and to collaborate on.> > > > >> > > > >> > > > > https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit?usp=sharing> > > > > >> > > > > Thanks,> > > > > Sumanth> > > > >> > > > > On Thu, May 23, 2019 at 12:04 PM Dinesh Joshi <dj...@apache.org> > wrote:> > > > >> > > > > > Sankalp,> > > > > >> > > > > > Great point. This is the page created for testing.> > > > > >> > > > > >> > > > > >> > > > >> > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+Quality%3A+Components+and+Test+Plans> > > > > > >> > > > > > I think we need to define the various release types and the exit> > > > criteria> > > > > > for each type of release. Anybody want to take a stab at this or > start> > > > a> > > > > > thread to discuss it?> > > > > >> > > > > > Thanks,> > > > > >> > > > > > Dinesh> > > > > >> > > > > >> > > > > > > On May 23, 2019, at 11:57 AM, sankalp kohli <ko...@gmail.com>> > > > > > wrote:> > > > > > >> > > > > > > Hi,> > > > > > > Is there a page where it is written what is expected from an> > > > alpha,> > > > > > > beta, rc and a 4.0 release?> > > > > > > Also how are we coming up with Q4 2019 timeline. Is this for > alpha,> > > > > beta,> > > > > > > rc or 4.0 release?> > > > > > >> > > > > > > Thanks,> > > > > > > Sankalp> > > > > > >> > > > > > > On Thu, May 23, 2019 at 11:27 AM Attila Wind > <attilaw@swf.technology> > > > >> > > > > > wrote:> > > > > > >> > > > > > >> +1+1+1 I read a blog post was talking about last sept(?) to > freeze> > > > > > >> features and start extensive testing. Maybe its really time to > hit> > > > it!> > > > > > :-)> > > > > > >>> > > > > > >> Attila Wind> > > > > > >>> > > > > > >> http://www.linkedin.com/in/attilaw> > > > > > >> Mobile: +36 31 7811355> > > > > > >>> > > > > > >>> > > > > > >> On 2019. 05. 23. 19:30, ajs6f wrote:> > > > > > >>> +1 in the fullest degree. A date that needs to be changed is > still> > > > > > >> enormously more attractive than no date at all.> > > > > > >>>> > > > > > >>> Adam Soroka> > > > > > >>>> > > > > > >>>> On May 23, 2019, at 12:01 PM, Sumanth Pasupuleti <> > > > > > >> spasupul...@netflix.com.INVALID> wrote:> > > > > > >>>>> > > > > > >>>> Having at least a ballpark target on the website will > definitely> > > > > help.> > > > > > >> +1> > > > > > >>>> on setting it to Q4 2019 for now.> > > > > > >>>>> > > > > > >>>> On Thu, May 23, 2019 at 8:52 AM Dinesh Joshi < > dj...@apache.org>> > > > > > wrote:> > > > > > >>>>> > > > > > >>>>> +1 on setting a date.> > > > > > >>>>>> > > > > > >>>>> Dinesh> > > > > > >>>>>> > > > > > >>>>>> On May 23, 2019, at 11:07 AM, Michael Shuler <> > > > > > mich...@pbandjelly.org>> > > > > > >>>>> wrote:> > > > > > >>>>>> We've had 4.0 listed as TBD release date for a very long > time.> > > > > > >>>>>>> > > > > > >>>>>> Yesterday, Alexander Dejanovski got a "when's 4.0 going to> > > > > release?"> > > > > > >>>>> question after his repair talk and he suggested possibly Q4 > 2019.> > > > > > This> > > > > > >>>>> morning Nate McCall hinted at possibly being close by > ApacheCon> > > > Las> > > > > > >> Vegas> > > > > > >>>>> in September. These got me thinking..> > > > > > >>>>>> Think we can we shoot for having a 4.0 alpha/beta/rc ready > to> > > > > > >>>>> announce/release at ApacheCon? At that time, we'll have > been> > > > frozen> > > > > > >> for 1> > > > > > >>>>> year, and I think we can. We'll GA release when it's ready, > but I> > > > > > >> think Q4> > > > > > >>>>> could be an realistic target.> > > > > > >>>>>> With that said, I'd like to change "TBD" on the downloads > page> > > > to> > > > > > >> "Est.> > > > > > >>>>> Q4 2019". We can always push or pull the estimate, but I > think> > > > it's> > > > > > >> time to> > > > > > >>>>> have a goal line. This lines up with ApacheCon nicely for a> > > > preview> > > > > > >> release.> > > > > > >>>>>> Any concerns or objections to editing the download page? > Have> > > > some> > > > > > >> other> > > > > > >>>>> goal timeframe in mind?> > > > > > >>>>>> --> > > > > > >>>>>> Warm regards,> > > > > > >>>>>> Michael> > > > > > >>>>>>> > > > > > >>>>>>> > > > > > > ---------------------------------------------------------------------> > > > > > >>>>>> To unsubscribe, e-mail: > dev-unsubscr...@cassandra.apache.org> > > > > > >>>>>> For additional commands, e-mail: > dev-h...@cassandra.apache.org> > > > > > >>>>>>> > > > > > >>>>>> > > > > > >>>>>> > > > > > ---------------------------------------------------------------------> > > > > > >>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org> > > > > > > >>>>> For additional commands, e-mail: > dev-h...@cassandra.apache.org> > > > > > >>>>>> > > > > > >>>>>> > > > > > >>>> > > > > > >>>> > > > ---------------------------------------------------------------------> > > > > > >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org> > > > > > >>> For additional commands, e-mail: dev-h...@cassandra.apache.org> > > > > > > >>>> > > > > > >>> > > > > >> > > > > >> > > > > > > ---------------------------------------------------------------------> > > > > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org> > > > > > For additional commands, e-mail: dev-h...@cassandra.apache.org> > > > > >> > > > > >> > > > >> > > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
