gt; Cassandra could take a look at it and let me know if anything is incorrect
> or inaccurate, or if I have missed anything.
>
> Thanks a lot for your help!
>
> Suli
>
>
> --
> Suli Yang
>
> Department of Physics
> University of Wisconsin Madison
>
&
NEWS.txt) https://goo.gl/GGI0aq
> [3]: https://issues.apache.org/jira/browse/CASSANDRA-13294
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
le here: http://people.apache.org/~mshuler
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/AYblr5
> [2]: (NEWS.txt) https://goo.gl/gIXxgR
>
> --
> Kind regards,
> Michael Shuler
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
le here: http://people.apache.org/~mshuler
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/17RivH
> [2]: (NEWS.txt) https://goo.gl/axKXys
>
> --
> Kind regards,
> Michael Shuler
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
le here: http://people.apache.org/~mshuler
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/ztSHQJ
> [2]: (NEWS.txt) https://goo.gl/nrengr
>
> --
> Kind regards,
> Michael Shuler
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
immediately applied locally.
--
Tyler Hobbs
DataStax <http://datastax.com/>
;, line
> 1521, in run
> self.inner_run()
> File "/usr/lib/python2.7/dist-packages/cqlshlib/copyutil.py", line
> 1544, in inner_run
> self.start_request(token_range, info)
> File "/usr/lib/python2.7/dist-packages/cqlshlib/copyutil.py", line
> 1573, in start_request
> metadata =
> session.cluster.metadata.keyspaces[self.ks].tables[self.table]
> KeyError: 'spielplatz_5'
> Child process 14957 died with exit code 1
> Child process 14961 died with exit code 1
> Child process 14968 died with exit code 1
> Exported 5 ranges out of 513 total ranges, some records might be missing
> Processed: 0 rows; Rate: 0 rows/s; Avg. rate: 0 rows/s
> 0 rows exported to 0 files in 0.311 seconds.
>
>
>
>
> Any hints?
>
>
> cheers,
> Michael
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
or all keys belong to it?
>
> Any similar ideas before?
>
>
> --
> Dikang
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
le here: http://people.apache.org/~mshuler
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/xc7jn6
> [2]: (NEWS.txt) https://goo.gl/O0C3Gb
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
> [0] http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
http://people.apache.org/~mshuler
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/TEMHqi
> [2]: (NEWS.txt) https://goo.gl/1w6Ec1
>
> --
> Kind regards,
> Michael Shuler
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
http://people.apache.org/~mshuler
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/b80Qe2
> [2]: (NEWS.txt) https://goo.gl/Aen2iN
>
> --
> Kind regards,
> Michael
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
gular cadence makes us less likely to slip
and fall behind on releases.
>
> Why not stick with monthly feature releases, but mark every third (or
> sixth) as a supported release that gets quarterly updates for 2-3 quarters?
>
That's also a good idea.
--
Tyler Hobbs
DataStax <http://datastax.com/>
;
> > > > jeff.ji...@crowdstrike.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>>> We did 3.1.1 and 3.2.1, so there’s SOME precedent for emergency
> > > > fixes,
> > > > >>>>> but we certainly didn’t/won’t go back and cut new releases from
> > > every
> > > > >>>>> branch for every critical bug in future releases, so I think we
> > > need
> > > > to
> > > > >>>>> draw the line somewhere. If it’s fixed in 3.7 and 3.0.x (x >=
> 6),
> > > it
> > > > seems
> > > > >>>>> like you’ve got options (either stay on the tick and go up to
> > 3.7,
> > > > or bail
> > > > >>>>> down to 3.0.x)
> > > > >>>>>
> > > > >>>>> Perhaps, though, this highlights the fact that tick/tock may
> not
> > be
> > > > the
> > > > >>>>> best option long term. We’ve tried it for a year, perhaps we
> > should
> > > > instead
> > > > >>>>> discuss whether or not it should continue, or if there’s
> another
> > > > process
> > > > >>>>> that gives us a better way to get useful patches into versions
> > > > people are
> > > > >>>>> willing to run in production.
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> On 9/14/16, 8:55 PM, "Jonathan Haddad"
> > wrote:
> > > > >>>>>
> > > > >>>>>> Common sense is what prevents someone from upgrading to yet
> > > another
> > > > >>>>>> completely unknown version with new features which have
> probably
> > > > broken
> > > > >>>>>> even more stuff that nobody is aware of. The folks I'm
> helping
> > > > right
> > > > >>>>>> deployed 3.5 when they got started because
> > > > >>>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__
> > > > cassandra.apache.org&d=DQIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kq
> > > > hAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=
> > > > MZ9nLcNNhQZkuXyH0NBbP1kSEE2M-SYgyVqZ88IJcXY&s=pLP3udocOcAG6k_
> > > > sAb9p8tcAhtOhpFm6JB7owGhPQEs&e=
> > > > >>>>> suggests
> > > > >>>>>> it's acceptable for production. It turns out using 4 of the
> > built
> > > > in
> > > > >>>>>> datatypes of the database result in the server being unable to
> > > > restart
> > > > >>>>>> without clearing out the commit logs and running a repair.
> That
> > > > screams
> > > > >>>>>> critical to me. You shouldn't even be able to install 3.5
> > without
> > > > the
> > > > >>>>>> patch I've supplied - that bug is a ticking time bomb for
> anyone
> > > > that
> > > > >>>>>> installs it.
> > > > >>>>>>
> > > > >>>>>> On Wed, Sep 14, 2016 at 8:12 PM Michael Shuler <
> > > > mich...@pbandjelly.org>
> > > > >>>>>> wrote:
> > > > >>>>>>
> > > > >>>>>>> What's preventing the use of the 3.6 or 3.7 releases where
> this
> > > > bug is
> > > > >>>>>>> already fixed? This is also fixed in the 3.0.6/7/8 releases.
> > > > >>>>>>>
> > > > >>>>>>> Michael
> > > > >>>>>>>
> > > > >>>>>>> On 09/14/2016 08:30 PM, Jonathan Haddad wrote:
> > > > >>>>>>>> Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not
> > back
> > > > >>>>> ported to
> > > > >>>>>>>> 3.5 as well, and it makes Cassandra effectively unusable if
> > > > someone
> > > > >>>>> is
> > > > >>>>>>>> using any of the 4 types affected in any of their schema.
> > > > >>>>>>>>
> > > > >>>>>>>> I have cherry picked & merged the patch back to here and
> will
> > > put
> > > > it
> > > > >>>>> in a
> > > > >>>>>>>> JIRA as well tonight, I just wanted to get the ball rolling
> > asap
> > > > on
> > > > >>>>> this.
> > > > >>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.
> > > > com_rustyrazorblade_cassandra_tree_fix-5Fcommitlog-
> > > 5Fexception&d=DQIBaQ&c=
> > > > 08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=
> > > > yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=
> > > > MZ9nLcNNhQZkuXyH0NBbP1kSEE2M-SYgyVqZ88IJcXY&s=ktY5tkT-
> > > > nO1jtyc0EicbgZHXJYl03DvzuxqzyyOgzII&e=
> > > > >>>>>>>>
> > > > >>>>>>>> Jon
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > http://twitter.com/tjake
> >
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
an package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: https://goo.gl/JKkE05 (CHANGES.txt)
> [2]: https://goo.gl/Hi8X71 (NEWS.txt)
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
7;re not doing this already, I suggest building the python driver with
Cython (check the driver docs). That makes serialization and
deserialization much more efficient.
--
Tyler Hobbs
DataStax <http://datastax.com/>
tracing
> reported it was returning 15K cells (which corresponds to the number of
> rows). I'd expect this in the second schema, but my understanding was that
> each element in a map was stored in it's own cell in current versions of
> cassandra, so a bit surprised by this.
>
> I'm using version 3.7 of cassandra and the datastax python drivers. Anyone
> got any insight into what happening here?
>
> -Ben
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
s IRC logging policy,
> > but
> > >>> the project / developers receives the best of both worlds – fast,
> real
> > >> time
> > >>> chat but also public archives/visibility for people who aren’t online
> > at
> > >> a
> > >>> given moment. The volume may be a bit higher than most of us have
> come
> > >>> expect from the list, but it brings the project closer to doing
> things
> > in
> > >>> The Apache Way, and we can give it an easily-filtered subject for
> folks
> > >> who
> > >>> don’t want that noise.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> http://twitter.com/tjake
> > >>
> >
> >
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
ol, or do
we want to piggyback on the Rx work, give up some control, and (hopefully)
get to the next, deeper optimizations sooner?
Thanks for any input on this topic.
--
Tyler Hobbs
DataStax <http://datastax.com/>
nowing
>>> > >> that
>>> > >>>> 2. has the small advantage of keeping the 3.0.x and 3.x
>>> > >>>> versions
>>> > >> released
>>> > >>>> more or less in lockstep).
>>> > >>>>
>>> > >>>>
>>> > >>>>
>>> > >>>>>
>>> > >>>>> On Thu, Jul 21, 2016 at 8:19 AM, Aleksey Yeschenko
>>> > >>>>> >> > >>>
>>> > >>>>> wrote:
>>> > >>>>>
>>> > >>>>>> I still think the issue is minor enough, and with 3.8 being
>>> > >>>>>> extremely delayed, and being a non-odd release, at that,
>>> > >>>>>> we’d be better off just pushing it.
>>> > >>>>>>
>>> > >>>>>> Also, I know we’ve been easy on -1s when voting on
>>> > >>>>>> releases, but I
>>> > >> want
>>> > >>>>> to
>>> > >>>>>> remind people in general that release votes can not be
>>> > >>>>>> vetoed and only require a majority of binding votes,
>>> > >>>>>> http://www.apache.org/foundation/voting.html#ReleaseVotes
>>> > >>>>>>
>>> > >>>>>>
>>> > >>>>>> -- AY
>>> > >>>>>>
>>> > >>>>>> On 21 July 2016 at 08:57:22, Sylvain Lebresne
>>> > >>>>>> (sylv...@datastax.com) wrote:
>>> > >>>>>>
>>> > >>>>>> Sorry but I'm (binding) -1 on this because of
>>> > >>>>>> https://issues.apache.org/jira/browse/CASSANDRA-12236.
>>> > >>>>>>
>>> > >>>>>> I disagree that knowingly releasing a version that will
>>> > >>>>>> temporarily
>>> > >>>> break
>>> > >>>>>> in-flight queries during upgrade, even if it's for a very
>>> > >>>>>> short
>>> > >>>>> time-frame
>>> > >>>>>> until re-connection, is ok. I'll note in particular that in
>>> > >>>>>> the test report, there is 74! failures in the upgrade tests
>>> > >>>>>> (for reference the
>>> > >>>> 3.7
>>> > >>>>>> test report had only 2 upgrade tests failure both with open
>>> > >>>>>> tickets).
>>> > >>>>> Given
>>> > >>>>>> that we have a known problem during upgrade, I don't really
>>> > >>>>>> buy the
>>> > >> "We
>>> > >>>>> are
>>> > >>>>>> assuming these are due to a recent downsize in instance
>>> > >>>>>> size that
>>> > >> these
>>> > >>>>>> tests run on" and that suggest to me the problem is not too
>>> > >>>>>> minor.
>>> > >>>>>>
>>> > >>>>>>
>>> > >>>>>> On Thu, Jul 21, 2016 at 6:18 AM, Dave Brosius <
>>> > >>>> dbros...@mebigfatguy.com>
>>> > >>>>>> wrote:
>>> > >>>>>>
>>> > >>>>>>> +1
>>> > >>>>>>>
>>> > >>>>>>>
>>> > >>>>>>> On 07/20/2016 05:48 PM, Michael Shuler wrote:
>>> > >>>>>>>
>>> > >>>>>>>> I propose the following artifacts for release as 3.8.
>>> > >>>>>>>>
>>> > >>>>>>>>
>>> > >>>>>>>> sha1: c3ded0551f538f7845602b27d53240cd8129265c Git:
>>> > >>>>>>>>
>>> > >>>>>>>>
>>> > >>>>>>
>>> > >>>>>
>>> > >>>>
>>> > >>
>>> >
>>>
>>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative
>>> > >>
>>> > >>>>>>>> Artifacts:
>>> > >>>>>>>>
>>> > >>>>>>>>
>>> > >>>>>>
>>> > >>>>>
>>> > >>>>
>>> > >>
>>> >
>>>
>>> https://repository.apache.org/content/repositories/orgapachecassandra-1123/org/apache/cassandra/apache-cassandra/3.8/
>>> > >>
>>> > >>>>>>>> Staging repository:
>>> > >>>>>>>>
>>> > >>>>>>>>
>>> > >>>>>>
>>> > >>>>>
>>> > >>>>
>>> > >>
>>> >
>>>
>>> https://repository.apache.org/content/repositories/orgapachecassandra-1123/
>>> > >>
>>> > >>>>>>>>
>>> > >>>>>>>> The debian packages are available here:
>>> > >>>>>>>> http://people.apache.org/~mshuler/
>>> > >>>>>>>>
>>> > >>>>>>>> The vote will be open for 72 hours (longer if needed).
>>> > >>>>>>>>
>>> > >>>>>>>>
>>> > >>>>>>>> [1]: http://goo.gl/oGNH0i (CHANGES.txt) [2]:
>>> > >>>>>>>> http://goo.gl/KjMtUn (NEWS.txt) [3]:
>>> > >>>>>>>> https://goo.gl/TxVLKo (3.8 Test Summary)
>>> > >>>>>>>>
>>> > >>>>>>>>
>>> > >>>>>>>
>>> > >>>>>>
>>> > >>>>>
>>> > >>>>>
>>> > >>>>>
>>> > >>>>> -- Jonathan Ellis Project Chair, Apache Cassandra co-founder,
>>> > >>>>> http://www.datastax.com @spyced
>>> > >>>>>
>>> > >>>>
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >>
>>> > >>
>>> > >
>>> >
>>> >
>>>
>>>
>>> --
>>> http://twitter.com/tjake
>>>
>>>
--
Tyler Hobbs
DataStax <http://datastax.com/>
,
> I am specifically asking this question for C* 2.0/2.1.
>
> Thanks in advance for your help.
>
> - Rajath
> ----
> Rajath Subramanyam
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
sitories/orgapachecassandra-1112/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/Yv15Qz (CHANGES.txt)
> > [2]: http://goo.gl/VyR9EG (NEWS.txt)
> > [3]: https://goo.gl/raz8ok (DataStax QA Report)
> >
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
t;=, and IN operators (see
https://issues.apache.org/jira/browse/CASSANDRA-6839).
--
Tyler Hobbs
DataStax <http://datastax.com/>
package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/IiNyVb (CHANGES.txt)
> [2]: http://goo.gl/ZAr03L (NEWS.txt)
> [3]: https://goo.gl/2jPtss (DataStax QA Report)
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/Yv15Qz (CHANGES.txt)
> [2]: http://goo.gl/VyR9EG (NEWS.txt)
> [3]: https://goo.gl/raz8ok (DataStax QA Report)
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
his file contain ? Is it compressed ? How do I read it ?
>
> Thanks in advance for sharing some information on this.
>
> - Rajath
> ----
> Rajath Subramanyam
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
ould interact with incremental repairs. If there
isn't a jira ticket for this already, can you open one with the scenario
above?
--
Tyler Hobbs
DataStax <http://datastax.com/>
7:48 PM, Rajath Subramanyam
wrote:
> Hello Cassandra-dev community,
>
> Does anyone know the JIRAs that affected the change in the SSTable format
> for C* 2.2 and later ?
>
> Thanks in advance.
>
> - Rajath
>
> Rajath Subramanyam
>
mailing list is a better place for the first
round of this conversation.
--
Tyler Hobbs
DataStax <http://datastax.com/>
” in a single table. We have an issue open to
> >>>> address this [3].
> >>>>
> >>>> I think it is reasonable to either deprecate Thrift immediately in 3.2
> >> or
> >>>> to wait until 10857 is committed in 3.4.
> >>>>
> >>>> [1]
> >>
> http://mail-archives.apache.org/mod_mbox/cassandra-dev/201403.mbox/%3ccaldd-zim6knmr7f_zcpvpqk0b2g919tttathiuofnvlztaw...@mail.gmail.com%3E
> >>>>
> >>>> [2]
> >>
> https://docs.google.com/spreadsheets/d/1FegCArZgj2DNAjNkcXi1n2Y1Kfvf6cdZedkMPYQdvC0/edit#gid=0
> >>>>
> >>>> [3] https://issues.apache.org/jira/browse/CASSANDRA-10857
> >
> >
> >
> > --
> >
> > Thanks,
> > Ryan Svihla
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
ized some releases and i noticed that not using java 7 features like
> multi catch and in java 8 do not use lambda expressions and others
> features, so i came by this email to know why the developers not using this
> features?
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
gt; > reconcile() in *ExpiringCell.java, instead of:
> >
> >if (cell instanceof DeletedCell)
> >return cell;
> >
> > use:
> >
> >if (cell instanceof DeletedCell)
> >return isLive() ? this : cell;
>
> The problem with sstable2json is that it does not support the CQL
> types as far as I can see and there isn't any indication as to modify
> it to do that. It seems like the CQL things are a layer above the
> SSTable.
>
> 2015-05-26 15:44 GMT+02:00 Tyler Hobbs :
> > I wou
d that my
> attempts to interpret them will result in a fragile result.
>
> Are there any suggestions? Existing libraries? Tips on how Cassandra
> parses the data itself? Pointers into the code to read? SSTable
> design doc?
>
> Thanks,
> /Malcolm
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
490ff9a70> will retry in 2 seconds
> 2015-05-26 10:34:27+ [] INFO: Unhandled error in Deferred:
> 2015-05-26 10:34:27+ [] Unhandled Error
> Traceback (most recent call last):
> Failure: twisted.internet.error.ConnectError: An error occurred
> while connecting: [Failure instance: Traceback (failure with no frames):
> : cafile must be None or a byte string
> ].
>
> Any hints about this?
>
> Thanks in advance,
> Jan
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
n: updatedtimestamp timestamp
> cql value:2013-10-17 10:35:23-0700
> json data: ["updatedtimestamp","2013-10-17 *10:35:23*
> -0700",1382031302954000]
>
> whats the issue in here or am I missing something?
>
>
> Regards,
> Arindam Bose
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
rmal
cql queries (outside of basic admin-type operations). What sort of API are
you envisioning?
--
Tyler Hobbs
DataStax <http://datastax.com/>
all access
> paths and boundary conditions per access path have prevented this
> CASSANDRA-8370 <https://issues.apache.org/jira/browse/CASSANDRA-8370> Sam
> Tunnicliffe cqlsh doesn't handle LIST statements correctly cqlsh untested
> functionality, no regression test? CASSAN
ends on Cassandra developers decission to devide source roots or
> not.
>
> Kind regards,
> Łukasz Dywicki
> —
> l...@code-house.org
> Twitter: ldywicki
> Blog: http://dywicki.pl
> Code-House - http://code-house.org
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
On Thu, Jan 8, 2015 at 2:23 PM, Philip Thompson <
philip.thomp...@datastax.com> wrote:
> I expect the benefits to grow as we make more radical changes
> to cassandra-dtest for cassandra 3.0.
>
What kinds of changes are you planning? Perhaps we can come up with good
alternativ
ding to commands and queries (e.g., jmx).
OOMs are handled in a better (more consistent) way with:
https://issues.apache.org/jira/browse/CASSANDRA-7507. That ticket may
explain a few things for you.
--
Tyler Hobbs
DataStax <http://datastax.com/>
:
> >
> > > A label works for me.
> > >
> > > But we also need a separate .txt file, or a section in NEWS.txt, for
> > those
> > > who can’t, or don’t want to follow the JIRA. Can’t realistically expect
> > > people to do that.
> > >
&g
d after we restore our data to the cluster. But we
> forget to restore statistic.db at that time. Is it the main reason?
>
>
> Could you help me on this issue?
> Thx
>
>
> Regards,
> Cong Ling
--
Tyler Hobbs
DataStax <http://datastax.com/>
nd
> decisions on issues that might impact client integration.
>
> In the discussion on CASSANDRA-8438 it was suggested that we might use
> labels to tag issues with implications to client integrators, so I wanted
> to float the idea here -- would maintainers be amenable to labeling
> client-impacting issues in JIRA?
>
>
> Adam
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
nd would mostly likely have to target 3.1.
--
Tyler Hobbs
DataStax <http://datastax.com/>
behavior (assuming a consistency level of ONE).
>
> It's my understanding from the documentation that consistency level one
> (which I am using) is about write consistency, not read consistency.
> Actually if I change it in cqlsh, cqlsh refuses to run the query.
>
The consistency level matters for both reads and writes.
--
Tyler Hobbs
DataStax <http://datastax.com/>
e you're saying "if I specify
a partition key, it only needs to query one node", which is also expected
behavior (assuming a consistency level of ONE).
By the way, this type of question is better suited for the user mailing
list than the dev mailing list.
--
Tyler Hobbs
DataStax <http://datastax.com/>
doesn't exist anymore in trunk. Do we simply use
> 'ant test'? Does it cover everything needed?
>
> [1] http://wiki.apache.org/cassandra/HowToContribute
>
> Regards, Heiko
--
Tyler Hobbs
DataStax <http://datastax.com/>
re, modification,
> distribution and / or publication of this message without the prior
> written consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error
> please delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses
> and other defects.
>
>
>
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
gt;
>
> Regards,
> Arindam Bose
> +1 469-231-3862
> Dallas, TX
>
>
> On Wed, Aug 27, 2014 at 4:54 PM, Tyler Hobbs wrote:
>
> > On Wed, Aug 27, 2014 at 3:28 PM, Arindam Bose
> > wrote:
> >
> > >
> > > Also, the code as below, is ret
clustering_column_2, ..., clustering_column_n, "mymap", map_key). To make
that work with your current code, you would do something like see if
cell.name().cql3ColumnName(baseCfs.metadata).toString().equals("mymap") is
true.
However, it would be more efficient to just limit yo
>
> > Added value:
> >
> > Insert into test(id, mymap) values ('1', {'1':'value1'});
> >
> > Then in my custom class I am trying to read mymap Cell.value() and
> > deserialize the ByteBuffervalue to get the full map content.
> >
> > But I am not getting the values as persisted in the mymap Column within
> > Cassandra.
> >
> > Is there anyone who can help?
> >
> >
> > Regards,
> > Arindam Bose
> >
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
log entries so that Rowkey corresponding to deleted
> columns gets printed in log file?
>
>
> Regards,
>
> Gaurav
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
stograms and there
> is no way to force values to expire after x minutes. The only thing I can
> see is that the last snapshot used to provide the median (or whatever you'd
> used instead) value is based on 1028 values.
> >
> > I'm wondering if providing the max value
On Wed, May 21, 2014 at 11:34 AM, Jonathan Ellis wrote:
> Which of those could someone else help with?
I'll take CASSANDRA-7120 (and CASSANDRA-7267, if needed).
--
Tyler Hobbs
DataStax <http://datastax.com/>
ting to use unit tests for some
CQL testing vs keeping everything in dtests?
[1]
https://github.com/thobbs/cassandra/blob/CASSANDRA-6875-2.0/test/unit/org/apache/cassandra/cql3/MultiColumnRelationTest.java
--
Tyler Hobbs
DataStax <http://datastax.com/>
the sender at the email above and delete this email and any attachments and
> destroy any copies thereof. Any review, retransmission, dissemination,
> copying or other use of, or taking any action in reliance upon, this
> information by persons or entities other than the intended recipient is
> strictly prohibited.
>
>
>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
xample describe_splits_ex in
> > > > org.apache.cassandra.hadoop.AbstractColumnFamilyInputFormat.
> > > >
> > > > Therefore, we had to keep thrift and native in our server but mainly,
> > the
> > > > CRUD query are through native protocol.
> > > > However, Jonathan says "*I don't know of any use cases for Thrift
> that
> > > > can't be **done in CQL"*. This statement makes me wonder maybe there
> is
> > > > something I don't know about native protocol yet.
> > > >
> > > > So, does anyone know how to do "describing the splits" and
> "describing
> > > the
> > > > local rings" using native protocol?
> > > >
> > > > Also, cqlsh uses python client, which is talking via thrift protocol
> > too.
> > > > Does it mean that it will be migrated to native protocol soon as
> well?
> > > >
> > > > Comments, pointers, suggestions are much appreciated.
> > > >
> > > > Many thanks,
> > > >
> > > > Shao-Chuan
> > > >
> > >
> >
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
Created https://issues.apache.org/jira/browse/CASSANDRA-6924 to investigate.
On Tue, Mar 25, 2014 at 1:50 PM, Tyler Hobbs wrote:
> After digging a bit, the regression is that data inserted immediately
> after secondary index creation may never get indexed.
>
> The operation ord
.
On Tue, Mar 25, 2014 at 11:14 AM, Tyler Hobbs wrote:
> -1
>
> I'm seeing a regression from 1.2.15 on secondary index queries (through
> Thrift) with a LongType key validator. Specifically, this test in pycassa
> is failing against 1.2.16-tentative:
> https://github.com/pyca
>
> 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/Cgiimu (CHANGES.txt)
> [2]: http://goo.gl/gvKkBm (NEWS.txt)
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
mysql. Where is the source code for this driver? Inside the same repository
> as the server. Cassandra should be the same way.
Other databases treat this issue differently, and there are a set of
tradeoffs. Mysql's decision may not be the best for Cassandra.
--
Tyler Hobbs
DataStax <http://datastax.com/>
decide how to resolve the
ambiguity in the spec.
Basically, I think you're looking for a reference implementation instead of
a spec. Perhaps a reference implementation would be useful, but that's a
separate debate.
--
Tyler Hobbs
DataStax <http://datastax.com/>
ra-1007/
>
> 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/dpGEUu (CHANGES.txt)
> [2]: http://goo.gl/6RPO71 (NEWS.txt)
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/MpQunt (CHANGES.txt)
> > [2]: http://goo.gl/VLWyfI (NEWS.txt)
> >
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
ld love to “turn it off” in the interim as it spams our
> ERROR monitoring - I’m guessing there is no other actual downside, since it
> just fails a subset of compaction runs
>
> Thanks,
>
> Graham.
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-163/org/apache/cassandra/apache-cassandra/2.0.2/
> > > Staging repository:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1
t; order of variable values C* will expect?
Your question isn't clear to me. Are you concerned with prepared
statements or non-prepared statements? What are you concerned about or
what are you trying to accomplish?
--
Tyler Hobbs
DataStax <http://datastax.com/>
;
That's correct.
--
Tyler Hobbs
DataStax <http://datastax.com/>
row
> > > data is provided. But in case of C* 1.2.5 and 1.2.8, I only get the
> row
> > > data. As far as I understand binary protocol, the message should have
> all
> > > the data to parse it. Does anyone know what I am missing?
> > >
> > > --
> > > Mosfeq
> > >
> > >
> >
> >
> > --
> > Tyler Hobbs
> > DataStax <http://datastax.com/>
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
response to the Select query is supposed to have metadata before row
> data is provided. But in case of C* 1.2.5 and 1.2.8, I only get the row
> data. As far as I understand binary protocol, the message should have all
> the data to parse it. Does anyone know what I am missing?
>
&
ngine, no prepared
> statements) and seems like pycassa performs almost 2 times better which
> makes it more preferable. It was simple inserts of couple thousands rows.
>
> Do I have to put up with all this and start using CQL?
>
> Thanks,
> --
> Vladimir Prudnikov
>
--
Tyler Hobbs
DataStax <http://datastax.com/>
On Fri, Jan 13, 2012 at 8:11 AM, Gary Dusbabek wrote:
>
> Not all languages Javascript make it easy to do binary.
PHP also goes in this boat, which leads me to agree with Gary.
--
Tyler Hobbs
DataStax <http://datastax.com/>
ll as
several new attributes for CfDef.
Feel free to email me if you have any questions about the changes.
--
Tyler Hobbs
Software Engineer, DataStax <http://datastax.com/>
Maintainer of the pycassa <http://github.com/pycassa/pycassa> Cassandra
Python client library
gt; > * ... ?
> > >
> > >
> > > What you can do
> > > ---
> > >
> > > * Play/test/experiment, and file bug reports. The Python driver's
> > > interactive interpreter is a good place to start (drivers/py/cqlsh).
> &
t java.lang.Thread.run(Thread.java:662)
>
>
> Thanks,
> Shotaro
>
Hi Shotaro,
I'm encountering the same issue, and I've opened
CASSANDRA-2282<https://issues.apache.org/jira/browse/CASSANDRA-2282>.
Could you comment on the ticket to document what conditions produced
Maybe you could take a look at
https://issues.apache.org/jira/browse/CASSANDRA-1562 ?
- Tyler
On Mon, Feb 14, 2011 at 10:17 AM, Eranda Sooriyabandara
<0704...@gmail.com>wrote:
> Hi all,
> Now I am quite comfortable with the Cassandra API and Cassandra-cli. So I
> am
> hoping to work on some tick
+1 Daniel.
I find the wiki to be completely unnavigable, and cleaner and clearer
documentation about the clients (including a possible per-language page)
might solve 50% of the problem.
- Tyler
On Fri, Dec 3, 2010 at 3:10 PM, Daniel Lundin wrote:
> On Fri, Dec 3, 2010 at 10:07 PM, Daniel Lundi
No, that's actually what I was specifically saying was not a good option.
Agreed.
On Fri, Dec 3, 2010 at 2:13 PM, Eric Evans wrote:
> On Fri, 2010-12-03 at 13:46 -0600, Tyler Hobbs wrote:
> > Personally, I like the Mongo drivers page:
> > http://www.mongodb.org/display/DO
Personally, I like the Mongo drivers page:
http://www.mongodb.org/display/DOCS/Drivers
I like the clear distinction between preferred and alternative clients
without a lot of clutter about release dates and supported versions. How do
we make that distinction, though? A "supported by Riptano" sec
I'm not completely sure I follow your scheme, but it's fairly to support
GT, LT, etc with your own index.
Use a row for your index where the columns names are the data values
you want to index. If you set the comparator type (in your example, this
would be LongType), you can perform a LT or GT qu
81 matches
Mail list logo
