[ 
https://issues.apache.org/jira/browse/CASSANDRA-16483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andres de la Peña updated CASSANDRA-16483:
------------------------------------------
          Fix Version/s:     (was: 4.0-beta)
                         4.0
                         3.11.11
                         3.0.25
          Since Version: 3.0.0
    Source Control Link: 
https://github.com/apache/cassandra/commit/9c7b69e4229b6817b248bcf5270a783eed1f9930
  
https://github.com/apache/cassandra-dtest/commit/7d10bdd19765bc337ee7bbe516c3a1e76391f5c0
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

> ColumnFilter::toString doesn't return a valid CQL fragment
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-16483
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16483
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Observability/Logging
>            Reporter: Sam Tunnicliffe
>            Assignee: Andres de la Peña
>            Priority: Normal
>             Fix For: 3.0.25, 3.11.11, 4.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> This was changed in CASSANDRA-16415 to include indications about queried vs 
> fetched reagular & static columns. However, the result is used by 
> {{AbstractReadQuery::toCQLString}}, which causes it to produce an illegal 
> query string.
> This breaks a couple of dtests because they're looking for CQL strings in 
> logs, which are no longer found:
> * 
> {{upgrade_tests/paging_test.py::TestPagingWithDeletions::test_failure_threshold_deletions}}
> * {{cql_test.py::TestCQLSlowQuery}} has a couple of failing tests, 
> {{test_local_query/test_remote_query}}
> We should also check audit and fql logs (and any other place where 
> {{toCQLString}} is used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to