you are on 3.0,
> So you are affected by UDT behaviour (stored as BLOB) mentioned in the
> JIRA.
>
> Cheers,
> Anup
>
> On 5 August 2018 at 23:29, shalom sagges wrote:
>
>> Hi All,
>>
>> Are there any known caveats for User Defined Types in Cassandra (vers
:
> Hi All,
>
> Are there any known caveats for User Defined Types in Cassandra (version
> 3.0)?
> One of our teams wants to start using them. I wish to assess it and see if
> it'd be wise (or not) to refrain from using UDTs.
>
>
> Thanks!
>
--
Anup Shirolka
Hi All,
Are there any known caveats for User Defined Types in Cassandra (version
3.0)?
One of our teams wants to start using them. I wish to assess it and see if
it'd be wise (or not) to refrain from using UDTs.
Thanks!
Hi all,
I am building an application that keeps a time-series record of clickstream
data (clicks, impressions, etc.). The data model looks something like:
CREATE TABLE clickstream (
userid text,
event_time timestamp,
interaction frozen interaction_type,
PRIMARY KEY (userid, timestamp)
)
Hi Alex,
I did so. Thanks for that hint.
Andi
From: Alex Popescu [al...@datastax.com]
Sent: 05 February 2015 18:14
To: user
Subject: Re: Problems with user defined types (cql) and Datastax Java Driver
Andreas,
Can you please post your question to the Java
Andreas,
Can you please post your question to the Java driver ml
https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user
as you'll have better chances to get an answer there.
thanks
On Thu, Feb 5, 2015 at 9:10 AM, Andreas Finke andreas.fi...@solvians.com
wrote:
Hi,
Hi,
I encountered the problem that in Java the Session does not create a valid
UserType for my corresponding CQL user defined type.
CQL_SCHEMA:
create keyspace if not exists quotes
WITH replication = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };
CREATE TYPE IF NOT EXISTS
.
T#
On Tue, Feb 25, 2014 at 12:10 PM, Sylvain Lebresne sylv...@datastax.comwrote:
Is there any documentation on how CQL clients should handle the new user
defined types coming in 2.1? There's nothing in the protocol specification
on how to handle custom types as far as I can see.
Can't say
CQL clients should handle the new user
defined types coming in 2.1? There's nothing in the protocol specification
on how to handle custom types as far as I can see.
Can't say there is much documentation so far for that. As for the spec,
it was written in a time where user defined types didn't
(I posted this on the client-dev list the other day, but that list seems
dead so I'm cross posting, sorry if it's the wrong thing to do)
Hi,
Is there any documentation on how CQL clients should handle the new user
defined types coming in 2.1? There's nothing in the protocol specification
on how
On Mon, Feb 24, 2014 at 7:52 PM, Theo Hultberg t...@iconara.net wrote:
(I posted this on the client-dev list the other day, but that list seems
dead so I'm cross posting, sorry if it's the wrong thing to do)
I didn't even realize there was a list for driver implementors - is
this used at all?
There hasn't been any activity (apart from my question) since december, and
only sporadic activity before that, so I think it's essentially dead.
http://www.mail-archive.com/client-dev@cassandra.apache.org/
T#
On Mon, Feb 24, 2014 at 10:34 PM, Ben Hood 0x6e6...@gmail.com wrote:
On Mon, Feb
12 matches
Mail list logo