Thank you Jeff. Please share once, the Patch is available for us to apply.
> On Jul 27, 2017, at 2:12 PM, Jeff Jirsa wrote:
>
>
>
> On 2017-07-20 08:46 (-0700), "Jeff Jirsa" wrote:
>>
>>
>> On 2017-07-20 08:17 (-0700), Nitan Kainth wrote:
>>> Jeff,
>>>
>>> It is really strange, look at b
On 2017-07-20 08:46 (-0700), "Jeff Jirsa" wrote:
>
>
> On 2017-07-20 08:17 (-0700), Nitan Kainth wrote:
> > Jeff,
> >
> > It is really strange, look at below log, I inserted your data and then few
> > additional; finally, the issue is reproduced:
> This is a bug, cqlsh is displaying the t
On 2017-07-20 08:17 (-0700), Nitan Kainth wrote:
> Jeff,
>
> It is really strange, look at below log, I inserted your data and then few
> additional; finally, the issue is reproduced:
>
..
> (6 rows)
> cqlsh> insert into test.t(a) values('b');
> cqlsh> select a,b, writetime (b) from test.t;
Jeff,
It is really strange, look at below log, I inserted your data and then few
additional; finally, the issue is reproduced:
[cqlsh 5.0.1 | Cassandra 3.0.10.1443 | DSE 5.0.4 | CQL spec 3.4.0 | Native
protocol v4]
Use HELP for help.
cqlsh> CREATE KEYSPACE test WITH replication = {'class':'Simp
This doesn't reproduce with the steps you're providing. There's clearly some
pre-existing data in the table, and some sort of operation on that table in the
past that isn't evident from your repro steps.
(oss-ccm) MacBook-Pro:~ jjirsa$ ccm create test -n 1 -s -v 3.0.10
Current cluster is now:
Same output Kurt,
[cqlsh 5.0.1 | Cassandra 3.0.10.1443 | DSE 5.0.4 | CQL spec 3.4.0 | Native
protocol v4]
Use HELP for help.
cqlsh> select a, writetime(b) from test.t;
a | writetime(b)
---+--
z | null
a | null
c | null
e | null
Works fine either case on 3.0.12
Subroto
> On Jul 18, 2017, at 2:41 PM, kurt greaves wrote:
>
> can you try select a, writetime(b) from test.t
> I heard of an issue recently where cqlsh reports null incorrectly if you
> query a column twice, wondering if it extends to this case with writetim
can you try select a, writetime(b) from test.t
I heard of an issue recently where cqlsh reports null incorrectly if you
query a column twice, wondering if it extends to this case with writetime.
insert into test.t (a ) values ('v’);
> On Jul 18, 2017, at 2:28 PM, Jonathan Haddad wrote:
>
> Since you didn't show all the queries you used, I made an assumption that
> you've inserted other data. Where is the query that inserted a="v"? I don't
> know how to answer the question if you're
Since you didn't show all the queries you used, I made an assumption that
you've inserted other data. Where is the query that inserted a="v"? I
don't know how to answer the question if you're not actually showing how to
reproduce the problem.
On Tue, Jul 18, 2017 at 12:24 PM Nitan Kainth wrote
Jonathan,
Please notice last rows with partition key values (w,v and t). they were
inserted same way and has write time values
> On Jul 18, 2017, at 2:22 PM, Jonathan Haddad wrote:
>
> This looks like expected behavior to me. You aren't inserting a value for b.
> Since there's no value, the
This looks like expected behavior to me. You aren't inserting a value for
b. Since there's no value, there's also no writetime.
On Tue, Jul 18, 2017 at 12:15 PM Nitan Kainth wrote:
> Hi,
>
> We see that null columns have writetime(column) populated for few columns
> and shows null for few othe
Hi,
We see that null columns have writetime(column) populated for few columns and
shows null for few other. Is it any bug or something else?
CREATE KEYSPACE test WITH replication = {'class': 'NetworkTopologyStrategy',
'us-east': '2'} AND durable_writes = true;
CREATE TABLE test.t (
a tex
13 matches
Mail list logo
