> [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.079 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.BytesReadTrackerTest
>> [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.058 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.EstimatedHistogramTest
>> [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.059 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.FBUtilitiesTest
>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.139 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.HexTest
>> [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.062 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.IntervalTest
>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.052 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.IntervalTreeTest
>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.147 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.LegacyBloomFilterTest
>> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.448 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.MergeIteratorTest
>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.073 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.MerkleTreeTest
>> [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 0.451 sec
>> [junit]
>> [junit] Testsuite: org.apache.cassandra.utils.SerializationsTest
>> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.814 sec
>> [junit]
>>
>> BUILD FAILED
>>
>> <https://builds.apache.org/job/Cassandra-quick/ws/cassandra/build.xml>:1036:
>> The following error occurred while executing this line:
>>
>> <https://builds.apache.org/job/Cassandra-quick/ws/cassandra/build.xml>:1022:
>> Some unit test(s) failed.
>>
>> Total time: 7 minutes 50 seconds
>> Build step 'Invoke Ant' marked build as failure
>> [TASKS] Skipping publisher since build result is FAILURE
>> Recording test results
>>
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
fsync (or low cached disk buffers), so no performance
> loss would occur
Right. What we're trying to fix here is having a single thread doing
the copying + checksumming being a bottleneck. The i/o pattern should
stay more or less the same.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co
DvuMV (CHANGES.txt)
> [2]: http://goo.gl/fNbTd (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
age are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/2HThC (CHANGES.txt)
> [2]: http://goo.gl/GhcPi (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
yte[] we deserialized it
from, so we don't need to reserialize it for the CommitLog. So I'd
avoid spending a ton of effort parallelizing the serialize, since in
the real world it's usually a no-op.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
gt; STG-Cass4 ERROR [ScheduledTasks:1] 2011-12-12 22:55:26,554 at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
> STG-Cass4 ERROR [ScheduledTasks:1] 2011-12-12 22:55:26,554 at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> STG-Cass4 ERROR [ScheduledTasks:1] 2011-12-12 22:55:26,554 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> STG-Cass4 ERROR [ScheduledTasks:1] 2011-12-12 22:55:26,554 at
> java.lang.Thread.run(Thread.java:619)
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
the freeze.
[1]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CASSANDRA+AND+fixVersion+%3D+%221.1%22+AND+resolution+%3D+Unresolved+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC&mode=hide
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-f
t; Vladimir Vivien
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
, they release 1 major version per
> year and they support 4 major versions for bugfixes and older postgresql
> versions are still common in production.
>
> Did you asked people running mission critical workloads about their opinion?
> Another possibility is to use ISV like Datastax t
ttp://wiki.apache.org/cassandra/Cassandra2475
>
> --
> Eric Evans
> Acunu | http://www.acunu.com | @acunu
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
existing practice
that keys are not updateable. Remaining columns will be updateable
since they will each map to a separate physical column.
(I've updated the wiki page.)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
I've updated the wiki page at
http://wiki.apache.org/cassandra/Cassandra2474 with a more in-depth
Background section that hopefully clears up where I'm going with this
sparse/dense business.
Eric mentioned on IRC that he's uneasy about the PRIMARY KEY syntax
implicitly using the first element of P
p.
However, we already have the "column names are always strings"
limitations with existing CQL DDL so it probably makes more sense to
consider it separately from transposition.
On Thu, Dec 29, 2011 at 3:22 PM, Eric Evans wrote:
> On Wed, Dec 28, 2011 at 1:05 PM, Jonathan Ellis wro
https://issues.apache.org/jira/browse/CASSANDRA-3685
On Thu, Dec 29, 2011 at 6:34 PM, Eric Evans wrote:
> On Thu, Dec 29, 2011 at 3:44 PM, Jonathan Ellis wrote:
>> That's to allow defining column names that are not text/utf8. So you
>> could have column name &quo
ed_at uuid,
body string,
posted_by string,
PRIMARY KEY(user_id, posted_at, posted_by),
VALUE(body)
);
(Open to better suggestions for that keyword.)
On Thu, Dec 29, 2011 at 3:13 PM, Eric Evans wrote:
> On Thu, Dec 29, 2011 at 12:04 PM, Jonathan Ellis wrote:
>> I've up
ows the
implementation to bleed through into the DDL. But, I can see the
advantage in regularity of having COMPOSITE VALUE adjacent to the PK
definition as well. So I'm fine either way, but I wanted to point
that out.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
o me is
>> that the lib directory is missing hadoop-core. So the question is, is this
>> lib dir just a legacy that should be removed, or should hadoop-core be added
>> to this lib dir, or am I completely confused?
>>
>> thanks,
>> dave
--
Jonathan Elli
tml for a
real-world example.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
ng down regressions
for us more than once).
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
pretty familiar with git. Perhaps he's just advocating rebasing
> locally? I am 100% in favor of that, and it sounds like Eric is too-
> rebase is almost always preferable to merge as long as you're not messing
> up any remote heads.
So, can I summarize our policy as "git p
On Wed, Jan 4, 2012 at 11:48 AM, paul cannon wrote:
> On Wed, Jan 4, 2012 at 11:40 AM, Jonathan Ellis wrote:
>
>> So, can I summarize our policy as "git pull --rebase"?
>>
>
> I'd rather have the normal case be to use topic branches for work, so
> --
merges from earlier branches. I thought that's
the main history you're worried about?
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
)
> So basically my question is how do we meld all those commits that will
> necessarily happen due to the nature of distributed reviews so that our
> main history don't look like shit? And if the answer is "we don't" then
> I'm not too fond of that solution.
> Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/d48a6c14
>
> Branch: refs/heads/trunk
> Commit: d48a6c14f370dfe97eb4e45c567ea9d1923914c6
> Parents: d371edf
> Author: Jonathan Ellis
> Authored: Tue Jan 10 12:56:23 2012 -0600
> Committer: Jonathan Ellis
]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CASSANDRA+AND+fixVersion+%3D+%221.1%22+AND+resolution+%3D+Unresolved+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC
On Mon, Dec 19, 2011 at 11:56 AM, Jonathan Ellis wrote:
> Just a reminder tha
, was already the
case except we missed range scans.)
On Tue, Jan 10, 2012 at 2:58 PM, Eric Evans wrote:
> On Tue, Jan 10, 2012 at 2:45 PM, Jonathan Ellis wrote:
>> Pedantic answer: yes, hence the NEWS entry
>>
>> More accurate answer: we've fixed a bug that allowed n
On Tue, Jan 10, 2012 at 3:59 PM, Brandon Williams wrote:
> On Tue, Jan 10, 2012 at 2:59 PM, Jonathan Ellis wrote:
>> I've tagged 7 tickets as "critical" [1] for 1.1. All of them deal
>> with CQL;
>
> Actually 1391 doesn't, but is quite important nonethe
rs (longer if needed).
>
> [1]: http://goo.gl/UTfwn (CHANGES.txt)
> [2]: http://goo.gl/EHlRp (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
he ratio seems a bit
> distorted.
>
> I'm tracing through the code, so any pointers to help me understand is
> appreciated
>
> thx
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
gt;
>
> On 1/12/12 6:18 PM, "Jonathan Ellis" wrote:
>
>>8x is pretty normal for JVM and bookkeeping overhead with the CLHCP.
>>
>>The SerializedCacheProvider is the default in 1.0 and is much
>>lighter-weight.
>>
>>On Thu, Jan 12, 2012 at 6:07
The Apache Cassandra PMC has voted to add Vijay as a committer. Thank
you Vijay, and we look forward to continuing to work with you!
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
on't you already have the binary encoding done for
the PHPCassa?
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
hat is *very* big argument against Strings. Sure we could add
>> yet another feature (or some hack) to handle binary, but why bother
>> when prepared statement with binary gives us that *and* we get 10%
>> faster writes even for small values.
>>
>> --
>> Sylvain
ail with the changes, if any, after the API is expected
> to be stable.
>
> Thanks,
>
> --
> Eric Evans
> Acunu | http://www.acunu.com | @acunu
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
epositories/orgapachecassandra-062/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/UTfwn (CHANGES.txt)
> [2]: http://goo.g
me grief with my testing of
> providers.
>
> I'm using 1.0.6
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
The Apache Cassandra PMC has voted to add Aaron as a committer.
Thanks for helping make Cassandra what it is today!
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
pbs/
> You can also read our technical report on PBS that has more technical
> detail: http://cs.berkeley.edu/Pubs/TechRpts/2012/EECS-2012-4.pdf
>
> Daniel Abadi recently blogged about the latency-consistency trade-off:
> http://dbmsmusings.blogspot.com/2011/12/replication-and-latency-c
ed
> completely. Is it true? Do you have any plans of removing Thift API, leaving
> CQL API only??
>
> thanks.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
ut I wanted to see what others thought first (those targets are
>> already a little unwieldy).
>>
>> Should we add this to run as part of "test", or leave it to be
>> configured separately by CI systems?
>
> I wouldn't mind keeping it out of 'ant test' bu
I've created a 1.1 branch in git. The freeze is on!
On Tue, Jan 10, 2012 at 2:59 PM, Jonathan Ellis wrote:
> I've tagged 7 tickets as "critical" [1] for 1.1. All of them deal
> with CQL; I strongly believe that 1.1 needs to be where CQL goes from
> being "
ded).
>
> [1]: http://goo.gl/ZOnuf (CHANGES.txt)
> [2]: http://goo.gl/EXtfL (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
der branch as well, use cherry-pick
- Turn on rebase for public branches ("git config branch.$name.rebase
true" for name in cassandra-0.8 through trunk)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
://goo.gl/XhPHr (CHANGES.txt)
> [2]: http://goo.gl/e5bjy (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
[moving to users list]
See http://wiki.apache.org/cassandra/CassandraLimitations
2012/2/15 晓峰 :
> I want to insert more and more columns into the super column,is there any
> problem?
>
>
>
>
> 晓峰
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Dat
providers using Ehcache and
> LinkedHashMap and both exhibit about the same memory usage (in my use
> case) as ConcurrentLinkedHashCache.
>
>
>
>
> On 1/12/12 9:02 PM, "Jonathan Ellis" wrote:
>
>>The serializing cache is basically optimal. Your problem is really
&g
into a Git repository by running
> $ git pull https://github.com/talmdal/cassandra trunk
>
> Alternatively you can review and apply these changes as the patch at
> https://github.com/apache/cassandra/pull/4.patch
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
arted hinted handoff for token: 0 with IP: /192.168.56.1
> INFO [HintedHandoff:1] 2012-02-20 14:44:53,815 HintedHandOffManager.java
> (line 373) Finished hinted handoff of 0 rows to endpoint /192.168.56.1
>
>
> I have a hint waiting to be deli
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/vDKh9 (CHANGES.txt)
> [2]: http://goo.gl/sbvXW (NEWS.txt)
--
Jonathan Ellis
uld you confirm my understanding is correct?
>
> regards,
> maki
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
rogress could be made here by allowing a "pack" of independent
> Cassandra nodes to be ran on a single host; somewhat (but nowhere near
> entirely) similar to a pre-fork model used by some UNIX-based servers.
>
> Input?
>
> --
> Rick Branson
> DataStax
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
On Tue, Mar 20, 2012 at 9:08 AM, Eric Evans wrote:
> On Tue, Mar 20, 2012 at 8:39 AM, Jonathan Ellis wrote:
>> I like this idea. It feels like a good 80/20 solution -- 80% of the
>> benefits, 20% of the effort. More like 5% of the effort. I can't
>> even enumerate
y since there are probably other
>> approaches that we can take to mitigate this, one of which Rick has
>> suggested in a separate sub-thread.
>
> Distributed rebuild means you can store more data per node with the
> same failure probabilities. This is frequently a limiting
uld suggest that the best way to mitigate that is, when you are
ready, to put together as detailed an implementation plan as possible
ahead of time before you start generating patchsets. Then we can put
some meat on the discussion more meaningful than vague "that scares
me" statemen
input, ideas and recommendations.
>
> Best Regards,
>
> Sam Overton
>
> [1] Staggering repair: https://issues.apache.org/jira/browse/CASSANDRA-3721
> [2] Project Voldemort, Design: http://project-voldemort.com/design.php
> [3] Dynamo:
> http://www.allthingsdistributed.com/files/amazon-dynamo-sosp2007.pdf
> [4] Ketama: Consistent Hashing:
> http://www.audioscrobbler.net/development/ketama/
> [5] Consistent Hashing:
> http://www.lexemetech.com/2007/11/consistent-hashing.html
>
> --
> Sam Overton
> Acunu | http://www.acunu.com | @acunu
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
ebian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/yNMo3 (CHANGES.txt)
> [2]: http://goo.gl/2AFuM (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder
; Lead Architect, Health Market Science (http://healthmarketscience.com)
> mobile:215.588.6024
> blog: http://weblogs.java.net/blog/boneill42/
> blog: http://brianoneill.blogspot.com/
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
etrieve just parts of objects efficiently,
rather than making column values just blobs with a bunch of special
case logic to introspect them. Which feels like a big step backwards
to me.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
eing worth giving up being able to deal
with your data from standard tools like cqlsh, IMO.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
mp in and help code that up, so much the better.)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
].
>> >>
>> >> Now on the client side, I'm using cassandra-cli with a custom type that
>> >> knows how to turn a byte[] into a JSON text and back. The only issue was
>> >> CASSANDRA-4081 where "assume" doesn't work with custom types.
for the unit tests for
> SliceQueryFilter. Searching only brings up one instance of it being used in
> the tests. Can someone point me in the right direction?
>
> Mark Dewey
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
esume rare) race condition
> scenario where 2 nodes would end up with same col. name and same col.
> timestamp but with a different col. value ?
> But then I wonder how to decide which value wins!
>
> Sincerely,
>
> Nicolas.
--
Jonathan Ellis
Project Chair, Apache C
gl/CsEDg (CHANGES.txt)
> [2]: http://goo.gl/4ByoR (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
Just List for the most part. If there are exactly two, maybe
Pair.
On Mon, Apr 2, 2012 at 6:30 PM, Mark Dewey wrote:
> Is there an object that is standard for specifying a compound range? (eg
> [W, X] + [Y, Z])
>
> Mark
--
Jonathan Ellis
Project Chair, Apache Cassandra
c
brian
>
> --
> Brian ONeill
> Lead Architect, Health Market Science (http://healthmarketscience.com)
> mobile:215.588.6024
> blog: http://weblogs.java.net/blog/boneill42/
> blog: http://brianoneill.blogspot.com/
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder
multiple
> IndexedSliceReader's for each of the required slice ranges and simply iterate
> though them.
>
> Which do you think is the better option? Am I making any sense, or am
> I completely off track?
>
> Any help would be greatly appreciated.
>
>
sitory.apache.org/content/repositories/orgapachecassandra-008/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/xmORw (CHANGES.txt)
> [2]
to test the IndexedBlockFetcher
> implementation (SimpleBlockFetcher is working fine) as none of the tests in
> ColumnFamilyStoreTest seem to use it (rowIndexEntry.columnsIndex().isEmpty()
> is always true in ISR). Is there an easy way to make the columns index be
> built for testing?
>
ifacts as well as the debian package are also available here:
>> >> http://people.apache.org/~slebresne/
>> >>
>> >> The vote will be open for 72 hours (longer if needed).
>> >>
>> >> [1]: http://goo.gl/xmORw (CHANGES.txt)
>> >> [2]: http://goo.gl/t0sSe (NEWS.txt)
>>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
py the way this is handled in NamesQueryFilter? Or am I
> missing something obvious?
>
> Mark
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/gjLT8 (CHANGES.txt)
> [2]: http://goo.gl/VsciE (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
in readMessageBegin
>> name = self.trans.readAll(sz)
>> File
>> "/usr/local/lib/python2.7/dist-packages/thrift/transport/TTransport.py",
>> line 58, in readAll
>> chunk = self.read(sz-have)
>> File
>> "/usr/local/lib/python2.7/dist-package
/goo.gl/KOOnk (CHANGES.txt)
> [2]: http://goo.gl/o1la0 (NEWS.txt)
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
ughts?
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
am not receiving Jira discussion updates, instead I am receiving jerkin
> builds now.
>
> -Samal
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
ies/orgapachecassandra-036/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/M9Y5A (CHANGES.txt)
> [2]: http://goo.gl/9xFe8 (NEWS.tx
ow I can check debian/changelog for the last "New Release" message and
> then find/guess the appropriate commit basing on author, date/time and
> commit message, but I don't think it's the best approach ;)
>
> --
> Kind regards,
> Michał
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
end this abstract
> class?
>
> Cheers,
> Sam
>
> [1]https://issues.apache.org/jira/browse/CASSANDRA-3147
> [2]https://issues.apache.org/jira/browse/CASSANDRA-2982
> [3]https://issues.apache.org/jira/browse/CASSANDRA-2915
--
Jonathan Ellis
Project Chair, Apache Cassandra
nt/repositories/orgapachecassandra-176/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/T2yfb (CHANGES.txt)
> [2]: http://goo.g
ere prefix
> compression?
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
;> > >
>> https://repository.apache.org/content/repositories/orgapachecassandra-176/
>> > >
>> > > The artifacts as well as the debian package are also available here:
>> > > http://people.apache.org/~slebresne/
>> > >
>> > >
patch queue management. We've written
>> up a tutorial here:
>> https://github.com/acunu/cassandra/wiki/TopGit-Tutorial
>>
>> == What's left? ==
>>
>> We haven't included any patches for tickets CASSANDRA-4123 and
>> CASSANDRA-4124 which relate to the replication strategy and repair.
>> Currently replication and repair "just work" with the current patches
>> without any additional changes required.
>>
>> CASSANDRA-4126 relates to testing. We're running virtual nodes builds
>> through our own test suites but we will also be writing new tests in
>> addition.
>>
>>
>> I look forward to your questions and comments!
>
>
>
> --
> Eric Evans
> Acunu | http://www.acunu.com | @acunu
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
;
> My plans now is to use crontab on my nodes to schedule the nodetool
> flush command to run on every minute.
>
> Do you guys see any other approach to check?
>
> --
> Atenciosamente,
> Fábio Caldas
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
e:
>> https://github.com/acunu/cassandra/wiki/TopGit-Tutorial
>>
>> == What's left? ==
>>
>> We haven't included any patches for tickets CASSANDRA-4123 and
>> CASSANDRA-4124 which relate to the replication strategy and repair.
>> Currently replication and repair "just work" with the current patches
>> without any additional changes required.
>>
>> CASSANDRA-4126 relates to testing. We're running virtual nodes builds
>> through our own test suites but we will also be writing new tests in
>> addition.
>>
>>
>> I look forward to your questions and comments!
>
>
>
> --
> Eric Evans
> Acunu | http://www.acunu.com | @acunu
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
NDRA-4124 which relate to the replication strategy and repair.
> Currently replication and repair "just work" with the current patches
> without any additional changes required.
>
> CASSANDRA-4126 relates to testing. We're running virtual nodes builds
> through our own test suites but we will also be writing new tests in
> addition.
>
>
> I look forward to your questions and comments!
>
>
> --
> Sam Overton
> Acunu | http://www.acunu.com | @acunu
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
901 - 986 of 986 matches
Mail list logo
