No, not really. It's just that dtests currently expect same behaviour for
3.x and up.
On Wed, Sep 28, 2016 at 8:41 PM Aleksey Yeschenko
wrote:
> We had one accidental merge from 3.0 into 3.9 (looking at you, you know
> who you are), so could be.
>
> --
> AY
>
> On 28 September 2016 at 17:48:27,
We had one accidental merge from 3.0 into 3.9 (looking at you, you know who you
are), so could be.
--
AY
On 28 September 2016 at 17:48:27, Philip Thompson
(philip.thomp...@datastax.com) wrote:
That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
accidentally also merged i
Might be I have only made differentiation for trunk and 2.x.
I'll investigate and report on JIRA. Thanks for assigning.
On Wed, Sep 28, 2016 at 6:48 PM Philip Thompson <
philip.thomp...@datastax.com> wrote:
> That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
> accidentally
That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
accidentally also merged into 3.9?
On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr Petrov <
oleksandr.pet...@gmail.com> wrote:
> LWTTester issues are leftovers from the bad merge in
> https://github.com/riptano/cassandra-dtest/pu
So I confirmed with Aleksey before firmly sticking foot in mouth, but you
CAN do this through Thrift -- Thrift has an API for sending a CQL string
via the Thrift interface.. We used to do something similar through Hector.
Not sure if this strictly fits your "is this possible via Thrift
interface"
LWTTester issues are leftovers from the bad merge in
https://github.com/riptano/cassandra-dtest/pull/1214
I've rebased and currently re-running tests.
On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <
philip.thomp...@datastax.com> wrote:
> Hi All,
>
> cassandra-3.9:
> ===
I have a similar set of problems. I will set the stage: in the past, for a
variety of reasons I had to create tables(column families) by time range
for an event processing system.
The man reason was expiring data (TTL) did not purge easily. It was easier
to simply truncate/drop old column families
Hi All,
cassandra-3.9:
===
testall: All passed!
===
dtest: 4 failures
cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest
.test_round_trip_with_authentication
Flaky test, needs a Jira ticket
cql_tests.L
No way to do that via Thrift I’m afraid, nor will there be one. Sorry.
--
AY
On 28 September 2016 at 16:43:58, Roman Bielik
(roman.bie...@openmindnetworks.com) wrote:
Hi,
in CQL it is possible to create a table with explicit ID: CREATE TABLE ...
WITH ID='xyz'.
Is something like this po
Hi,
in CQL it is possible to create a table with explicit ID: CREATE TABLE ...
WITH ID='xyz'.
Is something like this possible via Thrift interface?
There is an int32 "id" field in CfDef, but it has no effect on the table ID.
My problem is, that concurrent create table (add_column_family) request
* NOTICE *
This is the first release signed with key 0xA278B781FE4B2BDA by Michael
Shuler. Debian users will need to add the key to `apt-key` and the
process has been updated on
https://wiki.apache.org/cassandra/DebianPackaging and patch created for
source docs.
Either method will work:
c
Folks,
We've made some good efforts growing the committer pool recently and
it would be super cool to start getting more people involved in day to
day reviews and commits. You can find a guide of how to do this here:
http://cassandra.apache.org/doc/latest/development/how_to_commit.html
Honestly,
Github user hxzhaoyf commented on the issue:
https://github.com/apache/cassandra/pull/74
hi, I think the definition of address type need to update too, because
phone are UDT, and it should be frozen.
~~~
CREATE TYPE address (
street text,
city text,
zip
13 matches
Mail list logo
