Nice!
On Mon, Jun 28, 2010 at 4:08 PM, Eric Evans wrote:
>
> With the completion of https://issues.apache.org/jira/browse/INFRA-2556
> svnpubsub is now working for the website. That means that changes are
> applied to the live site immediately after committing it to
> site/publish.
>
> If you're
With the completion of https://issues.apache.org/jira/browse/INFRA-2556
svnpubsub is now working for the website. That means that changes are
applied to the live site immediately after committing it to
site/publish.
If you're accustomed to doing an `svn up' from /www/cassandra.a.o on
people.a.o,
Hello,
Are the currently checked in functional tests working? The instructions for
running them (http://wiki.apache.org/cassandra/HowToContribute) are not
working -- nosetests returns all failures -- and the init.py file does not
exist.
Thanks,
Marty
+1
On Fri, Jun 25, 2010 at 5:58 PM, Eric Evans wrote:
>
> As promised last week, here is the proposed 0.6.3 release. There have
> been a fair number of changes[1] since 0.6.2, so please look it over
> carefully and speak up if you notice any problems.
>
> SVN Tag: https://svn.apache.org/repos/asf
+1
-Chris
On Jun 28, 2010, at 9:09 AM, Brandon Williams wrote:
> On Fri, Jun 25, 2010 at 5:58 PM, Eric Evans wrote:
>
>>
>> As promised last week, here is the proposed 0.6.3 release. There have
>> been a fair number of changes[1] since 0.6.2, so please look it over
>> carefully and speak up i
On Fri, Jun 25, 2010 at 5:58 PM, Eric Evans wrote:
>
> As promised last week, here is the proposed 0.6.3 release. There have
> been a fair number of changes[1] since 0.6.2, so please look it over
> carefully and speak up if you notice any problems.
>
+1
-Brandon
+1
Matthieu
On Mon, Jun 28, 2010 at 5:33 AM, Gary Dusbabek wrote:
> +1
>
> On Fri, Jun 25, 2010 at 17:58, Eric Evans wrote:
> >
> > As promised last week, here is the proposed 0.6.3 release. There have
> > been a fair number of changes[1] since 0.6.2, so please look it over
> > carefully and s
In batch mode, we still block while the commit log is written. See
BatchCommitLogExecutorService.add(). That add() method is what gets
called in Table.apply().
Ah, yes. I did see the .add(), but I missed the .get() wait on the
future.
Thanks much.
--sriram.
+1
On Fri, Jun 25, 2010 at 17:58, Eric Evans wrote:
>
> As promised last week, here is the proposed 0.6.3 release. There have
> been a fair number of changes[1] since 0.6.2, so please look it over
> carefully and speak up if you notice any problems.
>
> SVN Tag: https://svn.apache.org/repos/asf/c
On Mon, Jun 28, 2010 at 04:44, Sriram Srinivasan wrote:
> Hiya.
>
> The architecture internals document and various presentations (such as
> http://www.slideshare.net/jhammerb/data-presentations-cassandra-sigmod) say
> something like the following:
>
> ... a row mutation is first written to the c
On Mon, Jun 28, 2010 at 02:29, Todd Nine wrote:
> Hi all,
> I thought the dev list would be more appropriate for this discussion. I'm
> having issues inserting Numeric Range keys in Lucandra and I've determined
> the issue (I think). Numeric keys are encoded with a trie data structure.
> The bi
Hiya.
The architecture internals document and various presentations (such as http://www.slideshare.net/jhammerb/data-presentations-cassandra-sigmod)
say something like the following:
... a row mutation is first written to the commit log before being
propagated to the memtable ...
This g
Hi all,
I thought the dev list would be more appropriate for this discussion. I'm
having issues inserting Numeric Range keys in Lucandra and I've determined
the issue (I think). Numeric keys are encoded with a trie data structure.
The bits of the underlying values are packed 7 bits at a time in
13 matches
Mail list logo
