[jira] [Comment Edited] (CASSANDRA-17393) pip tries to install futures in py3
[ https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505933#comment-17505933 ] Brad Schoening edited comment on CASSANDRA-17393 at 3/14/22, 1:08 AM: -- [~smiklosovic] I would propose changing 3.0 and 3.11 branches in requirement.txt, instead of setup, similar to the C* python driver. This should prevent it from being installed with py3. futures <=2.7.0 If we choose fix this, it should probably be separate from CASSANDRA-17417 was (Author: bschoeni): [~smiklosovic] I would propose changing 3.0 and 3.11 branches in requirement.txt, instead of setup, similar to the C* python driver. This should prevent it from being installed with py3. futures <=2.7.0 > pip tries to install futures in py3 > --- > > Key: CASSANDRA-17393 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17393 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > We've seen this problem in CI, and it's also seen (albeit extraneously) on > CASSANDRA-17293. This ticket is to explore removing futures from > requirements.txt, and it shouldn't be needed. -- 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] [Comment Edited] (CASSANDRA-17393) pip tries to install futures in py3
[ https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505933#comment-17505933 ] Brad Schoening edited comment on CASSANDRA-17393 at 3/14/22, 12:24 AM: --- [~smiklosovic] I would propose changing 3.0 and 3.11 branches in requirement.txt, instead of setup, similar to the C* python driver. This should prevent it from being installed with py3. futures <=2.7.0 was (Author: bschoeni): [~smiklosovic] I would propose changing 3.0 and 3.11 branches in requirement.txt instead of setup, similar to the C* python driver. This should prevent it from being installed with py3. futures <=2.7.0 > pip tries to install futures in py3 > --- > > Key: CASSANDRA-17393 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17393 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > We've seen this problem in CI, and it's also seen (albeit extraneously) on > CASSANDRA-17293. This ticket is to explore removing futures from > requirements.txt, and it shouldn't be needed. -- 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-17393) pip tries to install futures in py3
[ https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505933#comment-17505933 ] Brad Schoening commented on CASSANDRA-17393: [~smiklosovic] I would propose changing 3.0 and 3.11 branches in requirement.txt instead of setup, similar to the C* python driver. This should prevent it from being installed with py3. futures <=2.7.0 > pip tries to install futures in py3 > --- > > Key: CASSANDRA-17393 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17393 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > We've seen this problem in CI, and it's also seen (albeit extraneously) on > CASSANDRA-17293. This ticket is to explore removing futures from > requirements.txt, and it shouldn't be needed. -- 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] [Comment Edited] (CASSANDRA-17393) pip tries to install futures in py3
[ https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505925#comment-17505925 ] Brad Schoening edited comment on CASSANDRA-17393 at 3/13/22, 10:37 PM: --- [~e.dimitrova] yes, futures is only useful for 3.0 and 3.11. It would seem the Cassandra python driver mentions this dependency, but for an earlier python version. The Cassandra python driver requirements.txt states: -- futures <=2.2.0 Futures is not required for Python 3, but it works up through 2.2.0 (after which it introduced breaking syntax). This is left here to make sure install -r works with any runtime. When installing via setup.py, futures is omitted for Python 3, in favor of the standard library implementation.futures <=2.2.0 Futures is not required for Python 3, but it works up through 2.2.0 (after which it introduced breaking syntax). This is left here to make sure install -r works with any runtime. When installing via setup.py, futures is omitted for Python 3, in favor of the standard library implementation. -- [https://github.com/datastax/python-driver/blob/master/requirements.txt] was (Author: bschoeni): [~e.dimitrova] yes, futures is only useful for 3.0 and 3.11. It would seem the Cassandra python driver mentions this dependency, but for an earlier python version. The Cassandra python driver requirements.txt states: futures <=2.2.0 # Futures is not required for Python 3, but it works up through 2.2.0 (after which it introduced breaking syntax). # This is left here to make sure install -r works with any runtime. When installing via setup.py, futures is omitted # for Python 3, in favor of the standard library implementation.futures <=2.2.0 # Futures is not required for Python 3, but it works up through 2.2.0 (after which it introduced breaking syntax). # This is left here to make sure install -r works with any runtime. When installing via setup.py, futures is omitted # for Python 3, in favor of the standard library implementation. [https://github.com/datastax/python-driver/blob/master/requirements.txt] > pip tries to install futures in py3 > --- > > Key: CASSANDRA-17393 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17393 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > We've seen this problem in CI, and it's also seen (albeit extraneously) on > CASSANDRA-17293. This ticket is to explore removing futures from > requirements.txt, and it shouldn't be needed. -- 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-17393) pip tries to install futures in py3
[ https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505925#comment-17505925 ] Brad Schoening commented on CASSANDRA-17393: [~e.dimitrova] yes, futures is only useful for 3.0 and 3.11. It would seem the Cassandra python driver mentions this dependency, but for an earlier python version. The Cassandra python driver requirements.txt states: futures <=2.2.0 # Futures is not required for Python 3, but it works up through 2.2.0 (after which it introduced breaking syntax). # This is left here to make sure install -r works with any runtime. When installing via setup.py, futures is omitted # for Python 3, in favor of the standard library implementation.futures <=2.2.0 # Futures is not required for Python 3, but it works up through 2.2.0 (after which it introduced breaking syntax). # This is left here to make sure install -r works with any runtime. When installing via setup.py, futures is omitted # for Python 3, in favor of the standard library implementation. [https://github.com/datastax/python-driver/blob/master/requirements.txt] > pip tries to install futures in py3 > --- > > Key: CASSANDRA-17393 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17393 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > We've seen this problem in CI, and it's also seen (albeit extraneously) on > CASSANDRA-17293. This ticket is to explore removing futures from > requirements.txt, and it shouldn't be needed. -- 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-17393) pip tries to install futures in py3
[
https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505914#comment-17505914
]
Stefan Miklosovic commented on CASSANDRA-17393:
---
I mean that we might put this everyhere (into every branch) but it will be
effectively installed only for 3.0 and 3.11, no?
{code}
setup(
...
install_requires={
'futures; python_version == "2.7"'
}
)
{code}
Or do we trully want to just remove it from 4.0 and trunk?
> pip tries to install futures in py3
> ---
>
> Key: CASSANDRA-17393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17393
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
>
> We've seen this problem in CI, and it's also seen (albeit extraneously) on
> CASSANDRA-17293. This ticket is to explore removing futures from
> requirements.txt, and it shouldn't be needed.
--
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-17393) pip tries to install futures in py3
[
https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505912#comment-17505912
]
Ekaterina Dimitrova commented on CASSANDRA-17393:
-
{quote}bq. I think we need to do this for 3.0, 3.11, 4.0 and trunk but the
trick is that it would be installed dynamically based on what Python version we
run that in.
{quote}
Why removing it from 3.0 and 3.11? My understanding is that futures is a back
port to Python2 which we still use in 3.0 and 3.11, no?
> pip tries to install futures in py3
> ---
>
> Key: CASSANDRA-17393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17393
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
>
> We've seen this problem in CI, and it's also seen (albeit extraneously) on
> CASSANDRA-17293. This ticket is to explore removing futures from
> requirements.txt, and it shouldn't be needed.
--
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] [Comment Edited] (CASSANDRA-17393) pip tries to install futures in py3
[ https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505911#comment-17505911 ] Stefan Miklosovic edited comment on CASSANDRA-17393 at 3/13/22, 9:14 PM: - [~bschoeni] would you mind to create a patch for this as suggested by [~brandon.williams] (if you follow the link) before trying to get CASSANDRA-17417 in? (cc [~bsong]) I think we need to do this for 3.0, 3.11, 4.0 and trunk but the trick is that it would be installed dynamically based on what Python version we run that in. was (Author: smiklosovic): [~bschoeni] would you mind to create a patch for this as suggested by [~brandon.williams] (if you follow the link) before trying to get CASSANDRA-17417 in? (cc [~bsong]) > pip tries to install futures in py3 > --- > > Key: CASSANDRA-17393 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17393 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > We've seen this problem in CI, and it's also seen (albeit extraneously) on > CASSANDRA-17293. This ticket is to explore removing futures from > requirements.txt, and it shouldn't be needed. -- 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-17393) pip tries to install futures in py3
[ https://issues.apache.org/jira/browse/CASSANDRA-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505911#comment-17505911 ] Stefan Miklosovic commented on CASSANDRA-17393: --- [~bschoeni] would you mind to create a patch for this as suggested by [~brandon.williams] (if you follow the link) before trying to get CASSANDRA-17417 in? (cc [~bsong]) > pip tries to install futures in py3 > --- > > Key: CASSANDRA-17393 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17393 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > > We've seen this problem in CI, and it's also seen (albeit extraneously) on > CASSANDRA-17293. This ticket is to explore removing futures from > requirements.txt, and it shouldn't be needed. -- 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-16916) Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
[
https://issues.apache.org/jira/browse/CASSANDRA-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505910#comment-17505910
]
Ekaterina Dimitrova commented on CASSANDRA-16916:
-
[~djanand] , I can assure you I didn't forget this one, but a lot of things
happened this week and I was pulled to deal with some things in addition.
In order this patch not to get outdated again, I asked also a few other
contributors if they can look at it. We agreed whoever gets a bit of free time
first will just take it.
CC [~Bereng] , [~adelapena] , [~brandon.williams] and [~blerer]
In the meantime I pushed Jenkins CI
[here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1495/] so you can
see if something got broken and needs attention.
As we had a lot of troubles these days running CI I will also take a quick look
tomorrow to ensure nothing failed because of CI issues, not necessarily related
to your patch.
> Add support for IF EXISTS and IF NOT EXISTS in ALTER statements
> ---
>
> Key: CASSANDRA-16916
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16916
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Jogesh Anand
>Priority: Normal
> Fix For: 4.x
>
>
> It would make sense to add support for {{IF EXISTS}} and {{IF NOT EXISTS}} in
> the different {{ALTER}} statements.
> For example:
> * {{ALTER TABLE IF EXISTS myTable ...}}
> * {{ALTER TABLE myTable ADD IF NOT EXISTS ...}}
> * {{ALTER TABLE myTable DROP IF EXISTS ...}}
> * {{ALTER TYPE IF EXISTS myType ...}}
> * {{ALTER TYPE myType ADD IF NOT EXISTS ...}}
> +Additional info for newcomers:+
> In order to implement this change you will need to change the {{Parser.g}}
> ANTLR file located in the src/antlr directory and the java classes
> corresponding to the different alter statements located in the
> {{org.apache.cassandra.cql3.statements.schema}} package. You can look at the
> CreateTableStatement class to see how it was done there.
> The unit test for the CQL logic are located under
> {{org.apache.cassandra.cql3.validation}}
--
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-17428) Fail build when Ant is not of a certain version
[ https://issues.apache.org/jira/browse/CASSANDRA-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505908#comment-17505908 ] Stefan Miklosovic commented on CASSANDRA-17428: --- [~brandon.williams] [~paulo] would you +1 me? I ll apply that up to trunk on merge. https://ci-cassandra.apache.org/job/Cassandra-devbranch/1492/ https://github.com/apache/cassandra/pull/1489/files > Fail build when Ant is not of a certain version > --- > > Key: CASSANDRA-17428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17428 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Low > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x > > > As of writing this ticket, trunk is known to be buildable with Ant 1.10 and > users have reported build failures on Ant 1.9 (see CASSANDRA-16831). > There should be a check which fails the build if Ant used to build Cassanra > source code was not at least 1.10. -- 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] [Assigned] (CASSANDRA-13460) Diag. Events: Add local persistency
[
https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic reassigned CASSANDRA-13460:
-
Assignee: Stefan Miklosovic (was: Stefan Miklosovic)
> Diag. Events: Add local persistency
> ---
>
> Key: CASSANDRA-13460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13460
> Project: Cassandra
> Issue Type: Sub-task
> Components: Legacy/Observability
>Reporter: Stefan Podkowinski
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 0001-Add-persistency-for-events-to-system-keyspace.patch
>
>
> Some generated events will be rather less frequent but very useful for
> retroactive troubleshooting. E.g. all events related to bootstraping and
> gossip would probably be worth saving, as they might provide valuable
> insights and will consume very little resources in low quantities. Imaging if
> we could e.g. in case of CASSANDRA-13348 just ask the user to -run a tool
> like {{./bin/diagdump BootstrapEvent}} on each host, to get us a detailed log
> of all relevant events- provide a dump of all events as described in the
> [documentation|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst].
>
> This could be done by saving events white-listed in cassandra.yaml to a local
> table. Maybe using a TTL.
--
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] [Comment Edited] (CASSANDRA-13460) Diag. Events: Add local persistency
[
https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505905#comment-17505905
]
Stefan Miklosovic edited comment on CASSANDRA-13460 at 3/13/22, 7:54 PM:
-
Hi [~marcuse], would you give this a shot, please? I think you did a lot of
stuff around audit logs and I would like to know your opinion on the code
restructuring related to that. The above explanation of what I did would be
quite handy to go through to get easier into it.
was (Author: smiklosovic):
Hi [~marcuse], would you give this a shot, please? I think you did a lot of
stuff around audit logs and I would like to know your opinion on the code
restructuring related to that.
> Diag. Events: Add local persistency
> ---
>
> Key: CASSANDRA-13460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13460
> Project: Cassandra
> Issue Type: Sub-task
> Components: Legacy/Observability
>Reporter: Stefan Podkowinski
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 0001-Add-persistency-for-events-to-system-keyspace.patch
>
>
> Some generated events will be rather less frequent but very useful for
> retroactive troubleshooting. E.g. all events related to bootstraping and
> gossip would probably be worth saving, as they might provide valuable
> insights and will consume very little resources in low quantities. Imaging if
> we could e.g. in case of CASSANDRA-13348 just ask the user to -run a tool
> like {{./bin/diagdump BootstrapEvent}} on each host, to get us a detailed log
> of all relevant events- provide a dump of all events as described in the
> [documentation|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst].
>
> This could be done by saving events white-listed in cassandra.yaml to a local
> table. Maybe using a TTL.
--
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-13460) Diag. Events: Add local persistency
[
https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505905#comment-17505905
]
Stefan Miklosovic commented on CASSANDRA-13460:
---
Hi [~marcuse], would you give this a shot, please? I think you did a lot of
stuff around audit logs and I would like to know your opinion on the code
restructuring related to that.
> Diag. Events: Add local persistency
> ---
>
> Key: CASSANDRA-13460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13460
> Project: Cassandra
> Issue Type: Sub-task
> Components: Legacy/Observability
>Reporter: Stefan Podkowinski
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 0001-Add-persistency-for-events-to-system-keyspace.patch
>
>
> Some generated events will be rather less frequent but very useful for
> retroactive troubleshooting. E.g. all events related to bootstraping and
> gossip would probably be worth saving, as they might provide valuable
> insights and will consume very little resources in low quantities. Imaging if
> we could e.g. in case of CASSANDRA-13348 just ask the user to -run a tool
> like {{./bin/diagdump BootstrapEvent}} on each host, to get us a detailed log
> of all relevant events- provide a dump of all events as described in the
> [documentation|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst].
>
> This could be done by saving events white-listed in cassandra.yaml to a local
> table. Maybe using a TTL.
--
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-13460) Diag. Events: Add local persistency
[
https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-13460:
--
Authors: Stefan Miklosovic (was: Stefan Miklosovic)
Test and Documentation Plan: unit tests
Status: Patch Available (was: In Progress)
https://github.com/apache/cassandra/pull/1497
> Diag. Events: Add local persistency
> ---
>
> Key: CASSANDRA-13460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13460
> Project: Cassandra
> Issue Type: Sub-task
> Components: Legacy/Observability
>Reporter: Stefan Podkowinski
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 0001-Add-persistency-for-events-to-system-keyspace.patch
>
>
> Some generated events will be rather less frequent but very useful for
> retroactive troubleshooting. E.g. all events related to bootstraping and
> gossip would probably be worth saving, as they might provide valuable
> insights and will consume very little resources in low quantities. Imaging if
> we could e.g. in case of CASSANDRA-13348 just ask the user to -run a tool
> like {{./bin/diagdump BootstrapEvent}} on each host, to get us a detailed log
> of all relevant events- provide a dump of all events as described in the
> [documentation|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst].
>
> This could be done by saving events white-listed in cassandra.yaml to a local
> table. Maybe using a TTL.
--
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-17246) DOCS - Update changed config + JVM, guide post CASSANDRA-15234
[ https://issues.apache.org/jira/browse/CASSANDRA-17246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17246: Status: Review In Progress (was: Patch Available) > DOCS - Update changed config + JVM, guide post CASSANDRA-15234 > -- > > Key: CASSANDRA-17246 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17246 > Project: Cassandra > Issue Type: Task > Components: Documentation/NEWS.txt, Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > When CASSANDRA-15234 gets committed we need to update everywhere in the docs > the changed parameters names and we need to document: > * new types > * guide how to add new parameters > * some information about the backward compatibility network > Possibly missing some bullets, to be considered while doing the actual work. -- 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-17246) DOCS - Update changed config + JVM, guide post CASSANDRA-15234
[ https://issues.apache.org/jira/browse/CASSANDRA-17246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505902#comment-17505902 ] Ekaterina Dimitrova commented on CASSANDRA-17246: - All suggestions incorporated! Thank you > DOCS - Update changed config + JVM, guide post CASSANDRA-15234 > -- > > Key: CASSANDRA-17246 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17246 > Project: Cassandra > Issue Type: Task > Components: Documentation/NEWS.txt, Documentation/Website >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > When CASSANDRA-15234 gets committed we need to update everywhere in the docs > the changed parameters names and we need to document: > * new types > * guide how to add new parameters > * some information about the backward compatibility network > Possibly missing some bullets, to be considered while doing the actual work. -- 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-13460) Diag. Events: Add local persistency
[
https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505901#comment-17505901
]
Stefan Miklosovic commented on CASSANDRA-13460:
---
I would like to get back to this ticket and move it forward. It seems like
nothing has changed in this area since I implemented it.
> Diag. Events: Add local persistency
> ---
>
> Key: CASSANDRA-13460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13460
> Project: Cassandra
> Issue Type: Sub-task
> Components: Legacy/Observability
>Reporter: Stefan Podkowinski
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.x
>
> Attachments: 0001-Add-persistency-for-events-to-system-keyspace.patch
>
>
> Some generated events will be rather less frequent but very useful for
> retroactive troubleshooting. E.g. all events related to bootstraping and
> gossip would probably be worth saving, as they might provide valuable
> insights and will consume very little resources in low quantities. Imaging if
> we could e.g. in case of CASSANDRA-13348 just ask the user to -run a tool
> like {{./bin/diagdump BootstrapEvent}} on each host, to get us a detailed log
> of all relevant events- provide a dump of all events as described in the
> [documentation|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst].
>
> This could be done by saving events white-listed in cassandra.yaml to a local
> table. Maybe using a TTL.
--
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-17002) Gossipinfo should be available through a Virtual Table
[
https://issues.apache.org/jira/browse/CASSANDRA-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505894#comment-17505894
]
Stefan Miklosovic commented on CASSANDRA-17002:
---
Hi [~frankgh], I have started diag events in vtables here under
CASSANDRA-13460. I would love to cooperate on that with you or you can take it
from there and finish it.
We actually do have CEP for that here:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-12+Diagnostics+events+in+virtual+tables
Feel free to dump your ideas on CEP and we will definitely take it from there!
https://github.com/instaclustr/cassandra/commits/CASSANDRA-13460
> Gossipinfo should be available through a Virtual Table
> --
>
> Key: CASSANDRA-17002
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17002
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Virtual Tables
>Reporter: Dinesh Joshi
>Assignee: Francisco Guerrero
>Priority: Normal
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> The {{nodetool}} utility provides a utility to print out the {{gossipinfo}}
> for the cluster. The output is then printed out as text to stdout and
> consumed by operators and tools built around {{nodetool gossipinfo}}.
> With the introduction of virtual tables in Cassandra, the {{gossipinfo}}
> virtual table can help operators and the tools built around {{gossipinfo}} to
> consume the gossip information more easily by providing a tabular output of
> the data, which can be easily queried by different clients.
--
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-17417) Replace use of 'six' compatibility library with python 3 equivalents
[ https://issues.apache.org/jira/browse/CASSANDRA-17417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17417: -- Reviewers: Stefan Miklosovic Status: Review In Progress (was: Patch Available) > Replace use of 'six' compatibility library with python 3 equivalents > > > Key: CASSANDRA-17417 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17417 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > Attachments: six.pdf > > > _Six_ is a _Python_ 2 and 3 compatibility library. It provides simple > utilities for wrapping the differences between Python 2 and Python 3. It is > intended to support codebases that work on both Python 2 and 3. > Since CQLSH requires python version >= 3.6, its use can be replace with > native python 3 constructs. -- 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
