You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Ian Rose <ia...@fullstory.com> on 2015/01/21 22:55:34 UTC
get partition key from tombstone warnings?
When I see a warning like "Read 9 live and 5769 tombstoned cells in ...
<etc>" is there a way for me to see the partition key that this query was
operating on?
The description in the original JIRA ticket (
https://issues.apache.org/jira/browse/CASSANDRA-6042) reads as though
exposing this information was one of the original goals, but it isn't
obvious to me in the logs...
Cheers!
- Ian
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
UDF and DevCenter
Posted by "Andrew Cobley (Staff)" <a....@dundee.ac.uk>.
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: get partition key from tombstone warnings?
Posted by Philip Thompson <ph...@datastax.com>.
Ian,
Leaving a comment explaining your situation and how, as an operator of a
Cassandra Cluster, this would be valuable, would probably help most.
On Thu, Jan 22, 2015 at 6:06 AM, Paulo Ricardo Motta Gomes <
paulo.motta@chaordicsystems.com> wrote:
> Yep, you may register and log into the Apache JIRA and click "Vote for
> this issue", in the upper right-side of the ticket.
>
> On Wed, Jan 21, 2015 at 11:30 PM, Ian Rose <ia...@fullstory.com> wrote:
>
>> Ah, thanks for the pointer Philip. Is there any kind of formal way to
>> "vote up" issues? I'm assuming that adding a comment of "+1" or the like
>> is more likely to be *counter*productive.
>>
>> - Ian
>>
>>
>> On Wed, Jan 21, 2015 at 5:02 PM, Philip Thompson <
>> philip.thompson@datastax.com> wrote:
>>
>>> There is an open ticket for this improvement at
>>> https://issues.apache.org/jira/browse/CASSANDRA-8561
>>>
>>> On Wed, Jan 21, 2015 at 4:55 PM, Ian Rose <ia...@fullstory.com> wrote:
>>>
>>>> When I see a warning like "Read 9 live and 5769 tombstoned cells in ...
>>>> <etc>" is there a way for me to see the partition key that this query was
>>>> operating on?
>>>>
>>>> The description in the original JIRA ticket (
>>>> https://issues.apache.org/jira/browse/CASSANDRA-6042) reads as though
>>>> exposing this information was one of the original goals, but it isn't
>>>> obvious to me in the logs...
>>>>
>>>> Cheers!
>>>> - Ian
>>>>
>>>>
>>>
>>
>
>
> --
> *Paulo Motta*
>
> Chaordic | *Platform*
> *www.chaordic.com.br <http://www.chaordic.com.br/>*
> +55 48 3232.3200
>
Re: get partition key from tombstone warnings?
Posted by Paulo Ricardo Motta Gomes <pa...@chaordicsystems.com>.
Yep, you may register and log into the Apache JIRA and click "Vote for this
issue", in the upper right-side of the ticket.
On Wed, Jan 21, 2015 at 11:30 PM, Ian Rose <ia...@fullstory.com> wrote:
> Ah, thanks for the pointer Philip. Is there any kind of formal way to
> "vote up" issues? I'm assuming that adding a comment of "+1" or the like
> is more likely to be *counter*productive.
>
> - Ian
>
>
> On Wed, Jan 21, 2015 at 5:02 PM, Philip Thompson <
> philip.thompson@datastax.com> wrote:
>
>> There is an open ticket for this improvement at
>> https://issues.apache.org/jira/browse/CASSANDRA-8561
>>
>> On Wed, Jan 21, 2015 at 4:55 PM, Ian Rose <ia...@fullstory.com> wrote:
>>
>>> When I see a warning like "Read 9 live and 5769 tombstoned cells in ...
>>> <etc>" is there a way for me to see the partition key that this query was
>>> operating on?
>>>
>>> The description in the original JIRA ticket (
>>> https://issues.apache.org/jira/browse/CASSANDRA-6042) reads as though
>>> exposing this information was one of the original goals, but it isn't
>>> obvious to me in the logs...
>>>
>>> Cheers!
>>> - Ian
>>>
>>>
>>
>
--
*Paulo Motta*
Chaordic | *Platform*
*www.chaordic.com.br <http://www.chaordic.com.br/>*
+55 48 3232.3200
Re: get partition key from tombstone warnings?
Posted by Ian Rose <ia...@fullstory.com>.
Ah, thanks for the pointer Philip. Is there any kind of formal way to
"vote up" issues? I'm assuming that adding a comment of "+1" or the like
is more likely to be *counter*productive.
- Ian
On Wed, Jan 21, 2015 at 5:02 PM, Philip Thompson <
philip.thompson@datastax.com> wrote:
> There is an open ticket for this improvement at
> https://issues.apache.org/jira/browse/CASSANDRA-8561
>
> On Wed, Jan 21, 2015 at 4:55 PM, Ian Rose <ia...@fullstory.com> wrote:
>
>> When I see a warning like "Read 9 live and 5769 tombstoned cells in ...
>> <etc>" is there a way for me to see the partition key that this query was
>> operating on?
>>
>> The description in the original JIRA ticket (
>> https://issues.apache.org/jira/browse/CASSANDRA-6042) reads as though
>> exposing this information was one of the original goals, but it isn't
>> obvious to me in the logs...
>>
>> Cheers!
>> - Ian
>>
>>
>
Re: get partition key from tombstone warnings?
Posted by Philip Thompson <ph...@datastax.com>.
There is an open ticket for this improvement at
https://issues.apache.org/jira/browse/CASSANDRA-8561
On Wed, Jan 21, 2015 at 4:55 PM, Ian Rose <ia...@fullstory.com> wrote:
> When I see a warning like "Read 9 live and 5769 tombstoned cells in ...
> <etc>" is there a way for me to see the partition key that this query was
> operating on?
>
> The description in the original JIRA ticket (
> https://issues.apache.org/jira/browse/CASSANDRA-6042) reads as though
> exposing this information was one of the original goals, but it isn't
> obvious to me in the logs...
>
> Cheers!
> - Ian
>
>