[jira] [Updated] (CASSANDRA-17343) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2"
[
https://issues.apache.org/jira/browse/CASSANDRA-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17343:
--
Status: Changes Suggested (was: Review In Progress)
The examples aren't formatted correctly:
!c17343-examples-formatting.png|width=300!
They should look like this:
{code}
client_encryption_options:
keystore: conf/.keystore
keystore_password: cassandra
{code}
I've posted several suggestions directly on the PR. 👍
> WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2"
> --
>
> Key: CASSANDRA-17343
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17343
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Diogenese Topper
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c17343-examples-formatting.png
>
>
> This ticket is to capture the work associated with publishing the January
> 2022 blog "Tightening Security for Apache Cassandra Part: 2"
> If this blog cannot be published by the *February 4, 2022 publish date*,
> please contact me/suggest changes when possible in the pull request for the
> appropriate time that the blog will go live (on blog.adoc and in the blog
> post .adoc).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17343) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2"
[ https://issues.apache.org/jira/browse/CASSANDRA-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17343: -- Attachment: c17343-examples-formatting.png > WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2" > -- > > Key: CASSANDRA-17343 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17343 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17343-examples-formatting.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 2" > If this blog cannot be published by the *February 4, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17343) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2"
[ https://issues.apache.org/jira/browse/CASSANDRA-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17343: -- Status: Review In Progress (was: Patch Available) > WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2" > -- > > Key: CASSANDRA-17343 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17343 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 2" > If this blog cannot be published by the *February 4, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17343) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2"
[ https://issues.apache.org/jira/browse/CASSANDRA-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17343: -- Source Control Link: (was: https://github.com/apache/cassandra-website/pull/95/commits/82e7ffabee597c13fb323613cccf84bde5c929aa) > WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2" > -- > > Key: CASSANDRA-17343 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17343 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 2" > If this blog cannot be published by the *February 4, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15234) Standardise config and JVM parameters
[
https://issues.apache.org/jira/browse/CASSANDRA-15234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487801#comment-17487801
]
Ekaterina Dimitrova commented on CASSANDRA-15234:
-
Seems like CCM retagging worked with Jenkins but not with CircleCI anymore. In
order CircleCI to pickup the new tag, we need to add -e at the moment.
I opened a follow up ticket CASSANDRA-17351 to fix this. Until then, please,
use -e. More details sent to the mailing list
[here|https://lists.apache.org/thread/x6vojt50z5gcq9n3xfjvgb5cptnh36mz].
> 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: 4.1
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487796#comment-17487796 ] Ekaterina Dimitrova commented on CASSANDRA-17351: - Seems like even if Jenkins was struggling, the build in Jenkins finished at the end with a few new timeouts and port already in use (seems to me like the infra was not doing well today as the build prolonged hours and Jenkins was in status "shutting down") but ccm was properly picked up. Seems to me personally I have to figure out what Jenkins script do different then Circle in regards to CCM... > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.x > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487795#comment-17487795 ] Ekaterina Dimitrova commented on CASSANDRA-17351: - FYI I ran [here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1341/workflows/02956bb4-d837-4b9c-840b-ae592d599642/jobs/8622/parallel-runs/3?filterBy=ALL] J8 DTests on [~stefan.miklosovic] 's patch he was trying to test earlier today. With -e everything went smoothly there, downloading ccm and test completed green 100% > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.x > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Fix Version/s: 4.x > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.x > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17351) Pip doesn't install ccm every time
Ekaterina Dimitrova created CASSANDRA-17351: --- Summary: Pip doesn't install ccm every time Key: CASSANDRA-17351 URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 Project: Cassandra Issue Type: Task Reporter: Ekaterina Dimitrova In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to run without -e for ccm in order to address the moveable tag. That worked for some time until last night. I successfully retagged and now ccm is not re-installed in Circle CI. Jenkins picked stuff though. But it was acting unreliably and weird so rerunning now things there. Results pending. Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still pending results. I don't think this will be permanent solution and I am not sure whether it will affect also the previous branches in a way. We need to further investigate it and test. For now I will ask people to test with -e until we figure it out. CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Change Category: Quality Assurance Complexity: Normal Component/s: CI Priority: Urgent (was: Normal) Status: Open (was: Triage Needed) > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Urgent > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17236) Add support for short form of version to CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17236:
--
Reviewers: Brandon Williams, Stefan Miklosovic (was: Brandon Williams)
> Add support for short form of version to CQLSH
> --
>
> Key: CASSANDRA-17236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17236
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics
>Reporter: Madhavan
>Assignee: Yash Ladha
>Priority: Low
> Labels: lhf
> Fix For: 4.x
>
>
> Today we do only support the `–version` long option/form for cqlsh and this
> enhancement Jira is to request that we also offer a shorter version `-v` to
> cqlsh. This will have consistency benefits with other tools and even match
> with what we have at `bin/cassandra -v` option for instance.
> Today, `cqlsh` does support `--v` to get the version which is different than
> the single dashed short form that is available at many other tools. Thanks to
> Ekaterina for finding this. It looks like this is stemming from Python's
> parse mechanism which is detailed here,
> [https://docs.python.org/2.7/library/optparse.html#printing-a-version-string].
>
> [https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L194-L196]
> {quote}parser = optparse.OptionParser(description=description, epilog=epilog,
> usage="Usage: %prog [options] [host [port]]",
> version='cqlsh ' + version)
> {quote}
>
> {{$ bin/cqlsh --v}}
> {{cqlsh 6.0.0}}
> This looks like a weird implementation at Python. Both (\-\-help) and
> (\-\-version) options are stemming from here,
> [https://github.com/python/cpython/blob/2.7/Lib/optparse.py#L1248-L1256] and
> they did decide to ignore the short form option for version and it somehow
> automatically takes the (--v) option to spit the version info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17236) Add support for short form of version to CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17236:
--
Status: Review In Progress (was: Patch Available)
> Add support for short form of version to CQLSH
> --
>
> Key: CASSANDRA-17236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17236
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics
>Reporter: Madhavan
>Assignee: Yash Ladha
>Priority: Low
> Labels: lhf
> Fix For: 4.x
>
>
> Today we do only support the `–version` long option/form for cqlsh and this
> enhancement Jira is to request that we also offer a shorter version `-v` to
> cqlsh. This will have consistency benefits with other tools and even match
> with what we have at `bin/cassandra -v` option for instance.
> Today, `cqlsh` does support `--v` to get the version which is different than
> the single dashed short form that is available at many other tools. Thanks to
> Ekaterina for finding this. It looks like this is stemming from Python's
> parse mechanism which is detailed here,
> [https://docs.python.org/2.7/library/optparse.html#printing-a-version-string].
>
> [https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L194-L196]
> {quote}parser = optparse.OptionParser(description=description, epilog=epilog,
> usage="Usage: %prog [options] [host [port]]",
> version='cqlsh ' + version)
> {quote}
>
> {{$ bin/cqlsh --v}}
> {{cqlsh 6.0.0}}
> This looks like a weird implementation at Python. Both (\-\-help) and
> (\-\-version) options are stemming from here,
> [https://github.com/python/cpython/blob/2.7/Lib/optparse.py#L1248-L1256] and
> they did decide to ignore the short form option for version and it somehow
> automatically takes the (--v) option to spit the version info.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-7396) Allow selecting Map values and Set elements
[ https://issues.apache.org/jira/browse/CASSANDRA-7396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-7396: -- Description: Allow "SELECT map['key]" and "SELECT set['key']." (was: Allow "SELECT map['key]" and "SELECT list[index]." (Selecting a UDT subfield is already supported.) ) > Allow selecting Map values and Set elements > --- > > Key: CASSANDRA-7396 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7396 > Project: Cassandra > Issue Type: New Feature > Components: Legacy/CQL >Reporter: Jonathan Ellis >Assignee: Sylvain Lebresne >Priority: Normal > Labels: cql > Fix For: 4.0-alpha1, 4.0 > > Attachments: 7396_unit_tests.txt > > > Allow "SELECT map['key]" and "SELECT set['key']." -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
