You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by "Andrew Cobley (Staff)" <a....@dundee.ac.uk> on 2015/01/22 17:15:28 UTC
UDF and DevCenter
I’m not sure where to send “faults” for the DataStax Devcenter so I’ll send them here. If I define a UDT such as:
CREATE TYPE if not exists sensorsync.SensorReading (
fValue float,
sValue text,
iValue int
);
and a table
Create table if not exists sensorsync.Sensors(
name uuid,
insertion_time timestamp,
reading map <text,frozen<SensorReading>>,
Primary Key (name,insertion_time)
)
If I now want to insert data but not use all the fields in the UDT DevCenter flags it as a fault. So:
insert into sensorsync.Sensors (name,insertion_time,reading) values (7500e917-04b0-4697-ae7e-dbcdbf7415cb,'2015-01-01 02:10:05',{'sensor':{iValue:101},'sensor1':{fValue:30.5}});
Works ok (rund in devcenter and cqlsh) but dev centre flags the missing values with an error. Minor, but may throw people a curve.
Andy
The University of Dundee is a registered Scottish Charity, No: SC015096
Re: UDF and DevCenter
Posted by "Andrew Cobley (Staff)" <a....@dundee.ac.uk>.
Thanks Alex.
Andy
On 22 Jan 2015, at 16:54, Alex Popescu <al...@datastax.com>> wrote:
Thanks for the feedback Andy. I'll forward this to the DevCenter team.
Currently we have an email for sending feedback our way: devcenter-feedback@datastax.com<ma...@datastax.com>. And the good news is that in the next release there will be an integrated feedback form directly in DevCenter.
On Thu, Jan 22, 2015 at 8:15 AM, Andrew Cobley (Staff) <a....@dundee.ac.uk>> wrote:
I’m not sure where to send “faults” for the DataStax Devcenter so I’ll send them here. If I define a UDT such as:
CREATE TYPE if not exists sensorsync.SensorReading (
fValue float,
sValue text,
iValue int
);
and a table
Create table if not exists sensorsync.Sensors(
name uuid,
insertion_time timestamp,
reading map <text,frozen<SensorReading>>,
Primary Key (name,insertion_time)
)
If I now want to insert data but not use all the fields in the UDT DevCenter flags it as a fault. So:
insert into sensorsync.Sensors (name,insertion_time,reading) values (7500e917-04b0-4697-ae7e-dbcdbf7415cb,'2015-01-01 02:10:05',{'sensor':{iValue:101},'sensor1':{fValue:30.5}});
Works ok (rund in devcenter and cqlsh) but dev centre flags the missing values with an error. Minor, but may throw people a curve.
Andy
The University of Dundee is a registered Scottish Charity, No: SC015096
--
[:>-a)
Alex Popescu
Sen. Product Manager @ DataStax
@al3xandru
The University of Dundee is a registered Scottish Charity, No: SC015096
Re: UDF and DevCenter
Posted by Alex Popescu <al...@datastax.com>.
Thanks for the feedback Andy. I'll forward this to the DevCenter team.
Currently we have an email for sending feedback our way:
devcenter-feedback@datastax.com. And the good news is that in the next
release there will be an integrated feedback form directly in DevCenter.
On Thu, Jan 22, 2015 at 8:15 AM, Andrew Cobley (Staff) <
a.e.cobley@dundee.ac.uk> wrote:
>
> I’m not sure where to send “faults” for the DataStax Devcenter so I’ll
> send them here. If I define a UDT such as:
>
> CREATE TYPE if not exists sensorsync.SensorReading (
>
> fValue float,
> sValue text,
> iValue int
> );
>
> and a table
>
> Create table if not exists sensorsync.Sensors(
> name uuid,
> insertion_time timestamp,
> reading map <text,frozen<SensorReading>>,
> Primary Key (name,insertion_time)
> )
>
> If I now want to insert data but not use all the fields in the UDT
> DevCenter flags it as a fault. So:
>
> insert into sensorsync.Sensors (name,insertion_time,reading) values (
> 7500e917-04b0-4697-ae7e-dbcdbf7415cb,'2015-01-01 02:10:05',{'sensor':{
> iValue:101},'sensor1':{fValue:30.5}});
>
> Works ok (rund in devcenter and cqlsh) but dev centre flags the missing
> values with an error. Minor, but may throw people a curve.
>
> Andy
>
>
>
> The University of Dundee is a registered Scottish Charity, No: SC015096
>
--
[:>-a)
Alex Popescu
Sen. Product Manager @ DataStax
@al3xandru