Re: python web framework suggestions (for Cassandra Web UI) needed
Bottom line with this kind of a project is to go with what you're most familiar with. If you're equally unfamiliar with all frameworks, then the quality of documentation becomes more important. Personally, I'd take a hard look at Werkzeug--it's a library, not a framework. Which means you get to pick and choose what bits you want in a sort of a-la-carte way. In the end, similarly to Pylons or Django, you get a WSGI app that can be served out of the many different WSGI-aware web servers like Apache's mod_wsgi, gunicorn, cherrypy, or even the builtin wsgiref from the standard library. Anyway, I'm not sure if that helps or makes things more confusing :) Thanks, Eric Florenzano On Fri, Apr 9, 2010 at 10:23 AM, Pablo Cuadrado wrote: > It is indeed a web framework, and made for sys admins to interact with > Cassandra, not for hosting millions of users concurrently. > > And you're right: those are helloworld benchmarks. > > I was concerned a few days ago about the sync/async issue, browsing > over examples on Telephus, Twissandra, Lazyboy, Pycassa... then I > thought that Lazyboy is largely being used in production AFAIK, so > I've just kept it in my mind. > > However, the communication layer for the web UI, should (and hopefully > it will) be independent, in case we want to make this changes in the > future. > > On Fri, Apr 9, 2010 at 2:10 PM, Joseph Bowman > wrote: > > I don't really consider any hello world benchmarks valid, you'd want to > > investigate what your implementation would entail in different frameworks > > and do mini-benchmarks to validate which is faster. But, if it's just a > web > > framework, as Brandon said, I doubt performance will matter to any great > > degree. You'd be more concerned about Cassandra's performance, which is > > pretty darn good. > > > > On Fri, Apr 9, 2010 at 1:07 PM, Brandon Williams > wrote: > > > >> On Fri, Apr 9, 2010 at 12:04 PM, Pablo Cuadrado < > pablocuadr...@gmail.com > >> >wrote: > >> > >> > Yes, I'm planning on Lazyboy. > >> > > >> > The Performance part on the Tornado wiki is quite impressive. Do you > >> > think it's accurate? > >> > > >> > http://www.tornadoweb.org/documentation#performance > >> > >> > >> Using Lazyboy, you'd be mixing blocking sockets with a nonblocking event > >> loop, so performance is likely less than optimal. That said, I doubt > >> performance is a concern with a web UI. > >> > >> -Brandon > >> > > >
Re: Thoughts on issue 697 (Mitigate unpublished dependencies when using Cassandra with Maven)
On Sat, Apr 10, 2010 at 4:50 PM, Tatu Saloranta wrote: > On Sat, Apr 10, 2010 at 7:10 AM, Hannes Schmidt > wrote: > > On Fri, Apr 9, 2010 at 12:24 PM, Gary Dusbabek > wrote: > ... > >> Why? "To make things easier for mvn users" isn't enough of an > >> argument to convince me. > >> > > > > I can't really help you with that. Maven users make up a considerable > > segment of your potential user base. If making life easier for them > doesn't > > motivate you, I am not sure what does. It surely isn't a sense for the > > community. > > How about stopping asking for others do the work, and doing it > yourself, if YOU care so much? > This approach (of actually DOING something) has been suggested > multiple times: and next comments is likely to be along lines of "just > fuck off". > Tatu, I can't do the work. If I could, I already would have done it. And it's not because I don't have the time. Only the project owners can deploy the jars to a public Maven repository. This is minimal amount of work that would be necessary simply to save the work another contributor had already done. I made the mistake of mingling two issues: A) moving the build for the trunk to Maven (which is clearly not going to happen) and B) saving the efforts that went into the Maven POM which was contributed for 0.5. The latter should have been the primary focus of the discussion and I am responsible for distracting from it. > And please do not talk as if you represented significant segment of > unhappy users -- if there are others, they are quite capable of > speaking up to support your request. > Given the hostility of your response they might be afraid to speak up? But seriously, most of them probably don't have the time to research this problem or "whine" in here. They just deploy the respective artifacts to their local repo and get on with life which is probably what I should have done in the first place. Unfortunately, this would only work for 0.5, though, not for the trunk because the POM there is not functional. This is where A) comes in and I do realize that I should be the one to fix the POM and ask for the artifacts to be deployed. But this is exactly the same kind of work that went into the 0.5 POM. And did the committers live up to their part? Assuming that the team does not want to move to Maven, there are two alternatives to A): Either the Ant/Ivy build could deploy the artifacts to a Maven repository or someone could generate stub POMs for Cassandra. I don't think stubs are gonna make it into a public repo so these would have to be published somewhere else. > > Pardon my french, but this seems to fall to the repugnant category of > "not enough time to help, enough time to whine". > Hmm, yeah, I really don't appreciate your tone. > -+ Tatu +- > > ps. I'm not part of project team, and above opinion is my personal > one. Just so there's no misunderstanding. >
Is there any way to enable the multiple super column names at a time?
Hi, I don't know whether I have missed anything here, but can we get columns for multiple Super Column Names at a time, like what we can do for Keys (by key range or list of keys) or columns (by column range or column list)? While I'm doing the work with Cassandra, I usually think the structure like this: KS - CF - Key - Super Column - Column But looks like I should change it to something like: KS - CF - Super Column - Key - Column Since CF-SuperColumn are combined within a single parameter: ColumnParent, and they are usually unique (single) in a query. Regards, Dop
[VOTE] Release 0.6.0 (final)
It's been about a week and half since rc1 and there aren't any serious issues so I propose we release. The tag and artifacts below should differ from rc1 only in that the versioning was updated. SVN Tag: https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.6.0 0.6.0 artifacts: http://people.apache.org/~eevans Additionally, the ASF press team has put together a press release to announce this release and our graduation to a TLP. They send these things out on Tuesdays, so unless there are any complaints, I'd like to limit the duration of this vote to 24 hours. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.6.0 (final)
+1 -Chris On Apr 11, 2010, at 6:55 PM, Eric Evans wrote: > > It's been about a week and half since rc1 and there aren't any serious > issues so I propose we release. The tag and artifacts below should > differ from rc1 only in that the versioning was updated. > > SVN Tag: > https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.6.0 > 0.6.0 artifacts: http://people.apache.org/~eevans > > Additionally, the ASF press team has put together a press release to > announce this release and our graduation to a TLP. They send these > things out on Tuesdays, so unless there are any complaints, I'd like > to limit the duration of this vote to 24 hours. > > > -- > Eric Evans > eev...@rackspace.com > > >
Re: [VOTE] Release 0.6.0 (final)
+1 FWIW there's no need to wait once the whole PMC voted. On Sun, Apr 11, 2010 at 6:55 PM, Eric Evans wrote: > > It's been about a week and half since rc1 and there aren't any serious > issues so I propose we release. The tag and artifacts below should > differ from rc1 only in that the versioning was updated. > > SVN Tag: > https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.6.0 > 0.6.0 artifacts: http://people.apache.org/~eevans > > Additionally, the ASF press team has put together a press release to > announce this release and our graduation to a TLP. They send these > things out on Tuesdays, so unless there are any complaints, I'd like > to limit the duration of this vote to 24 hours. > > > -- > Eric Evans > eev...@rackspace.com > > > >
Re: [VOTE] Release 0.6.0 (final)
On Sun, 2010-04-11 at 19:00 -0700, Matthieu Riou wrote: > FWIW there's no need to wait once the whole PMC voted. Sure. But it's been awhile since we've had the entire PMC participate in a release vote. :) -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.6.0 (final)
+1 On Sun, Apr 11, 2010 at 8:55 PM, Eric Evans wrote: > > It's been about a week and half since rc1 and there aren't any serious > issues so I propose we release. The tag and artifacts below should > differ from rc1 only in that the versioning was updated. > > SVN Tag: > https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.6.0 > 0.6.0 artifacts: http://people.apache.org/~eevans > > Additionally, the ASF press team has put together a press release to > announce this release and our graduation to a TLP. They send these > things out on Tuesdays, so unless there are any complaints, I'd like > to limit the duration of this vote to 24 hours. > > > -- > Eric Evans > eev...@rackspace.com > > > >
Re: [VOTE] Release 0.6.0 (final)
+1 2010/4/12 Jonathan Ellis > +1 > > On Sun, Apr 11, 2010 at 8:55 PM, Eric Evans wrote: > > > > It's been about a week and half since rc1 and there aren't any serious > > issues so I propose we release. The tag and artifacts below should > > differ from rc1 only in that the versioning was updated. > > > > SVN Tag: > > https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.6.0 > > 0.6.0 artifacts: http://people.apache.org/~eevans > > > > Additionally, the ASF press team has put together a press release to > > announce this release and our graduation to a TLP. They send these > > things out on Tuesdays, so unless there are any complaints, I'd like > > to limit the duration of this vote to 24 hours. > > > > > > -- > > Eric Evans > > eev...@rackspace.com > > > > > > > > >
