-2-7939377b73c6#.zco8oq3dj
-- Jack Krupansky
On Thu, May 5, 2016 at 10:55 AM, Eric Evans
wrote:
> On Wed, May 4, 2016 at 12:14 PM, Jonathan Ellis wrote:
> > On Wed, May 4, 2016 at 2:27 AM, Sylvain Lebresne
> > wrote:
> >
> >> On Tue, May 3, 2016 at 6:57 PM, Eric
adoc, either for the setter or the field.
-- Jack Krupansky
On Tue, May 3, 2016 at 12:57 PM, Eric Evans
wrote:
> On Mon, May 2, 2016 at 11:26 AM, Sylvain Lebresne
> wrote:
> > Looking forward to other's opinions and feedbacks on this proposal.
>
> We might want to leave ju
best comment it. And then once
the dust settles and there is some general consensus on what the
real/implied rules/guidelines should be, based on the reality of that
initial module, pick another module.and see if the deduced rules/guidelines
from the first module can be methodically applied.
-- Jack
e full upgrade path to
3.x rather than go halfway since sometimes halfhearted measures don't get
the degree of attention needed for the full effort, such as people trying
to cut corners to do it on the cheap.
-- Jack Krupansky
On Sat, Apr 23, 2016 at 10:50 PM, Anuj Wadehra <
anujw_2...@y
duction 2.x system to 3.x somewhere
down the road. No need to rush, but don't wait until the last minute
either. And I suspect that you won't even want to think about upgrading 2.x
to 4.x - IOW, upgrade to 3.x well before 3.x EOL.
-- Jack Krupansky
On Sat, Apr 23, 2016 at 3:28 PM, An
Thanks for the prompt service!
-- Jack Krupansky
On Tue, Apr 19, 2016 at 12:16 PM, Benjamin Lerer <
benjamin.le...@datastax.com> wrote:
> Done. Thanks for reporting the problem.
>
> On Tuesday, April 19, 2016, Benjamin Lerer
> wrote:
>
> > I will fix it. I am the
3/functions/AggregateFcts.java#L362
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/functions/AggregateFcts.java#L398
Let me know if this needs a Jia ticket or if somebody can just fix it
without the paperwork.
-- Jack Krupansky
Here's a recent security assessment discussion - list of questions,
proposed response, and discussion, which you might find helpful, courtesy
of Oleg Yusim:
https://docs.google.com/document/d/13-yu-1a0MMkBiJFPNkYoTd1Hzed9tgKltWi6hFLZbsk/edit?ts=56c3a130#heading=h.xq6exsjcda8
-- Jack Krup
ps://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/functions/AggregateFcts.java#L885
So, sorry for the confusion. Some comments in the grammar would have helped.
And it's not in the DataStax doc, but that's another issue I can follow up
on.
-- Jack Krupansky
O
andra/blob/trunk/src/antlr/Parser.g#L276
Does this need a Jira, or can somebody just fix it to avoid the paperwork?
Or, was this actually supposed to work and the bug is some missing
implementation?
Thanks.
-- Jack Krupansky
ommend that your own statement be added there instead.
-- Jack Krupansky
On Mon, Apr 11, 2016 at 5:03 PM, Jeremiah Jordan
wrote:
> As I understand it "COMPACT STORAGE" only has meaning in the CQL parser
> for backwards compatibility as of 3.0. The on disk storage is not affected
>
.yaml
For (outdated) reference:
http://wiki.apache.org/cassandra/StorageConfiguration
-- Jack Krupansky
ORAGE? That will still leave the question of how to migrate a non-Thrift
COMPACT STORAGE table (i.e., used for performance by a CQL-oriented
developer rather than Thrift compatibility per se) to pure CQL.
-- Jack Krupansky
MAX_MUTATION_SIZE)
{
throw new IllegalArgumentException(String.format("Mutation of
%s is too large for the maximum size of %s",
FBUtilities.prettyPrintMemory(totalSize),
FBUtilities.prettyPrintMemory(MAX_MUTATION_SIZE)));
}
-- Jack Krupansky
ache.org/jira/browse/CASSANDRA-10256
-- Jack Krupansky
Interesting question as to what the future of the nodetool wiki page is.
You can get more/full detail in the DataStax doc:
https://docs.datastax.com/en/cassandra/3.x/cassandra/tools/toolsNodetool.html
-- Jack Krupansky
On Mon, Apr 4, 2016 at 12:08 PM, Anubhav Kale
wrote:
> There are oth
indexes extend it?
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/index/internal/CassandraIndex.java
-- Jack Krupansky
On Sun, Mar 6, 2016 at 11:03 PM, Henry Manasseh
wrote:
> Thank you. This is a perfect class for to start experimenting with.
>
>
> O
That doesn't give you a desirable answer to your question, but that's the
best you can do for now, other than the sweet nothings that a sales person
is willing to whisper in your ear for private consumption in the name of
enhancing revenue for DataStax.
-- Jack Krupansky
On Wed, Feb
ix release", but in fact the latest
critical patch (3.2.1) is against a feature release, not a bug fix release.
Should that simply say "... against the most recent tick-tock release"
regardless of whether it was an even (feature) or odd (bug fix) release?
Thanks.
-- Jack Krupansky
Thanks, Jonathan. The end-of-life (EOL) question is still dangling out
there - when does 3.x go off support, after 3.x+3 or six months after 4.0?
Or... six months after 5.0?
-- Jack Krupansky
On Thu, Jan 14, 2016 at 6:15 PM, Jonathan Ellis wrote:
> On Thu, Jan 14, 2016 at 4:26 PM, J
al"
section? In which case, the question of criteria for defining "stable
release" remains, unless it becomes no different than the latest tick-tock
release.
-- Jack Krupansky
On Thu, Jan 14, 2016 at 12:57 PM, Anuj Wadehra
wrote:
> Hi Jonathan,
> Thanks for the crisp communica
pick it will go EOL within just a few
months.
-- Jack Krupansky
On Thu, Jan 14, 2016 at 11:39 AM, Mark Dewey wrote:
> Let's do a couple examples:
>
>1. Current release: 3.4.0, bug found in 3.1.0 that also exists in
>subsequent versions; the bug fix will be ported b
It's best to ask usage and data modeling questions on the user email list -
this list is the dev list, for development of Cassandra itself, not for
development of applications.
See:
http://cassandra.apache.org/
-- Jack Krupansky
On Thu, Dec 31, 2015 at 8:36 AM, Lior Menashe
wrote:
ch replica.) Again, Carl, Jake, et al need
to review precise details.
-- Jack Krupansky
On Wed, Dec 2, 2015 at 1:02 AM, Michael Edge wrote:
> Yes - good point.
>
> I've updated the text for the write path page below - could you please
> review? Once my understanding is correct I
I just remembered... the new Materialized View support in 3.0 - writes to
the materialized views get triggered when a write occurs to the base table.
That needs to be in the write path flow/description as well.
-- Jack Krupansky
On Mon, Nov 30, 2015 at 9:30 PM, Michael Edge
wrote:
> Thanks
s" to "The data is stored for a
default period of 3 hours, configurable using the
max_hint_window_in_ms property
in cassandra.yaml."
-- Jack Krupansky
On Mon, Nov 30, 2015 at 2:24 AM, Michael Edge
wrote:
> Write path docs updated on Wiki - please review diagram/text and let me
&g
same.
-- Jack Krupansky
On Fri, Jul 10, 2015 at 1:43 AM, Ajay Chander wrote:
> Any one here came across a situation like this ? Thank you!
>
> On Thursday, July 9, 2015, Ajay Chander wrote:
>
> > More information:
> >
> >
> > Below is my cassandra bolt.
> >
.
Who is doing the queries, the program in which Cassandra is embedded, or an
external client over the net?
-- Jack Krupansky
On Tue, Mar 24, 2015 at 5:38 AM, Ersin Er wrote:
> Hi all,
>
> As far as I understand it seems to be enough to initialize and activate
> CassandraDaemon f
The "default_time_to_live" property for CREATE TABLE. See:
http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/tabProp.html
That's in the DataStax CQL doc, but I don't see it in the Apache Cassandra
CQL spec:
https://cassandra.apache.org/doc/cql3/CQL-2.0.htm
29 matches
Mail list logo
