[
https://issues.apache.org/jira/browse/CASSANDRA-17560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525967#comment-17525967
]
David Capwell commented on CASSANDRA-17560:
-------------------------------------------
found out the issue for the python upgrade test failures, CASSANDRA-10537 made
a change to both python-dtest and trunk, and when this CI run was kicked off
that patch wasn't in trunk, but it picked up the python-dtest changed, which
caused this error
Rebased again and trying 1 more time
> Migrate track_warnings to more standard naming conventions and use latest
> configuration types rather than long
> --------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17560
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17560
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.1
>
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> Track warnings currently is nested which is discouraged at the moment. It
> also was before the config standards patch which moved storage typed longs to
> a new DataStorageSpec type, we should migrate the configs there.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
