[
https://issues.apache.org/jira/browse/CASSANDRA-15234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452143#comment-17452143
]
Ekaterina Dimitrova commented on CASSANDRA-15234:
-------------------------------------------------
Quick update - I figured it is purely pip3 issue how we install ccm. The time
things worked was when I had a bug in my code, but in general CCM is not
changing to my new version when I change it in requirements.txt
What I found in CircleCI logs:
{code:java}
Collecting ccm
Cloning https://github.com/ekaterinadimitrova2/ccm.git (to revision
CASSANDRA-15234) to
/tmp/pip-install-dvfww32x/ccm_727b34808faa4db6904e104a715a22d2
Running command git clone -q https://github.com/ekaterinadimitrova2/ccm.git
/tmp/pip-install-dvfww32x/ccm_727b34808faa4db6904e104a715a22d2
Running command git checkout -b CASSANDRA-15234 --track origin/CASSANDRA-15234
Switched to a new branch 'CASSANDRA-15234'
Branch 'CASSANDRA-15234' set up to track remote branch 'CASSANDRA-15234' from
'origin'.
Resolved https://github.com/ekaterinadimitrova2/ccm.git to commit
ee52d120ea34d44500c64bfb3b9d3f517b0865f1
{code}
But then
{code:java}
pip3 freeze
{code}
output shows:
{code:java}
ccm @
git+https://github.com/riptano/ccm.git@ce612ea71587bf263ed513cb8f8d5dfcf7c8dadb
{code}
> Standardise config and JVM parameters
> -------------------------------------
>
> Key: CASSANDRA-15234
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15234
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Benedict Elliott Smith
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 5.x
>
> Attachments: CASSANDRA-15234-3-DTests-JAVA8.txt
>
>
> We have a bunch of inconsistent names and config patterns in the codebase,
> both from the yams and JVM properties. It would be nice to standardise the
> naming (such as otc_ vs internode_) as well as the provision of values with
> units - while maintaining perpetual backwards compatibility with the old
> parameter names, of course.
> For temporal units, I would propose parsing strings with suffixes of:
> {{code}}
> u|micros(econds?)?
> ms|millis(econds?)?
> s(econds?)?
> m(inutes?)?
> h(ours?)?
> d(ays?)?
> mo(nths?)?
> {{code}}
> For rate units, I would propose parsing any of the standard {{B/s, KiB/s,
> MiB/s, GiB/s, TiB/s}}.
> Perhaps for avoiding ambiguity we could not accept bauds {{bs, Mbps}} or
> powers of 1000 such as {{KB/s}}, given these are regularly used for either
> their old or new definition e.g. {{KiB/s}}, or we could support them and
> simply log the value in bytes/s.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
