[jira] [Commented] (CASSANDRA-14655) Upgrade C* to use latest guava (27.0)
[ https://issues.apache.org/jira/browse/CASSANDRA-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945595#comment-16945595 ] Sumanth Pasupuleti commented on CASSANDRA-14655: [~mck] Updated patch file to include the BulkLoader UTs you have added. Also, updated diff: https://github.com/apache/cassandra/compare/trunk...sumanth-pasupuleti:guava_27_trunk?expand=1 > Upgrade C* to use latest guava (27.0) > - > > Key: CASSANDRA-14655 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14655 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Low > Labels: 4.0-feature-freeze-review-requested > Fix For: 4.x > > Attachments: 14655-4.0.txt > > > C* currently uses guava 23.3. This JIRA is about changing C* to use latest > guava (26.0). Originated from a discussion in the mailing list. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14655) Upgrade C* to use latest guava (27.0)
[ https://issues.apache.org/jira/browse/CASSANDRA-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumanth Pasupuleti updated CASSANDRA-14655: --- Attachment: 14655-4.0.txt > Upgrade C* to use latest guava (27.0) > - > > Key: CASSANDRA-14655 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14655 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Low > Labels: 4.0-feature-freeze-review-requested > Fix For: 4.x > > Attachments: 14655-4.0.txt > > > C* currently uses guava 23.3. This JIRA is about changing C* to use latest > guava (26.0). Originated from a discussion in the mailing list. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14655) Upgrade C* to use latest guava (27.0)
[ https://issues.apache.org/jira/browse/CASSANDRA-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumanth Pasupuleti updated CASSANDRA-14655: --- Attachment: (was: 14655-4.0.txt) > Upgrade C* to use latest guava (27.0) > - > > Key: CASSANDRA-14655 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14655 > Project: Cassandra > Issue Type: Improvement > Components: Dependencies >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Low > Labels: 4.0-feature-freeze-review-requested > Fix For: 4.x > > > C* currently uses guava 23.3. This JIRA is about changing C* to use latest > guava (26.0). Originated from a discussion in the mailing list. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-10190) Python 3 support for cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945587#comment-16945587
]
Andy Tolbert edited comment on CASSANDRA-10190 at 10/7/19 4:58 AM:
---
{quote}
I think it's worth updating the driver to a newer version
{quote}
I just read the comments earlier in the thread about the driver, mainly this
one:
{quote}
Finally, extracting the checked in driver is something we'll look into. But
that is a longpole and strictly not needed for Python 3 compatibility.
{quote}
Agree with that, don't think that should hold things up, it can be done out of
band. Noticed that I had already opened up a ticket for updating the python
driver a while back for a different reason ([CASSANDRA-14872]), and there's
probably other 4.0 specific reasons it needs to be updated, so would be good to
do that separately.
was (Author: andrew.tolbert):
{quote}
I think it's worth updating the driver to a newer version
{quote}
I just read the comments earlier in the thread about the driver, mainly this
one:
{quote}
Finally, extracting the checked in driver is something we'll look into. But
that is a longpole and strictly not needed for Python 3 compatibility.
{quote}
Agree with that, don't think that should hold things up, it can be done out of
band. Noticed that I had already opened up a ticket of updating the python
driver a while back for a different reason ([CASSANDRA-14872]), and there's
probably other 4.0 specific reasons it needs to be updated, so would be good to
do that separately.
> Python 3 support for cqlsh
> --
>
> Key: CASSANDRA-10190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10190
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
>Reporter: Andrew Pennebaker
>Assignee: Patrick Bannister
>Priority: Normal
> Labels: cqlsh
> Fix For: 4.0, 4.0-alpha
>
> Attachments: 0001-Update-six-to-1.12.0.patch,
> 0002-Simplify-version-specific-logic-by-using-six.moves-a.patch,
> coverage_notes.txt
>
>
> Users who operate in a Python 3 environment may have trouble launching cqlsh.
> Could we please update cqlsh's syntax to run in Python 3?
> As a workaround, users can setup pyenv, and cd to a directory with a
> .python-version containing "2.7". But it would be nice if cqlsh supported
> modern Python versions out of the box.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14872) Update to version of python driver and update cqlsh to use driver metadata for virtual tables
[
https://issues.apache.org/jira/browse/CASSANDRA-14872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945588#comment-16945588
]
Andy Tolbert commented on CASSANDRA-14872:
--
Newer versions of the python driver also fix some issues around python3, so
upgrading would also benefit [CASSANDRA-10190].
> Update to version of python driver and update cqlsh to use driver metadata
> for virtual tables
> -
>
> Key: CASSANDRA-14872
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14872
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL, Legacy/Tools
>Reporter: Andy Tolbert
>Priority: Normal
>
> When virtual tables were implemented ([CASSANDRA-7622]), cqlsh.py was updated
> to parse virtual keyspace metadata by making queries to the
> {{system_virtual_schema}} table and included a TODO:
> {code:python}
> # TODO remove after virtual tables are added to connection metadata
> {code}
> Since python driver 3.15.0 (released in August), the driver now parses
> virtual keyspace metadata. It would be good to update the bundled python
> driver and simplify cqlsh code to utilize its capability to parse virtual
> tables.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-10190) Python 3 support for cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945587#comment-16945587
]
Andy Tolbert commented on CASSANDRA-10190:
--
{quote}
I think it's worth updating the driver to a newer version
{quote}
I just read the comments earlier in the thread about the driver, mainly this
one:
{quote}
Finally, extracting the checked in driver is something we'll look into. But
that is a longpole and strictly not needed for Python 3 compatibility.
{quote}
Agree with that, don't think that should hold things up, it can be done out of
band. Noticed that I had already opened up a ticket of updating the python
driver a while back for a different reason ([CASSANDRA-14872]), and there's
probably other 4.0 specific reasons it needs to be updated, so would be good to
do that separately.
> Python 3 support for cqlsh
> --
>
> Key: CASSANDRA-10190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10190
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
>Reporter: Andrew Pennebaker
>Assignee: Patrick Bannister
>Priority: Normal
> Labels: cqlsh
> Fix For: 4.0, 4.0-alpha
>
> Attachments: 0001-Update-six-to-1.12.0.patch,
> 0002-Simplify-version-specific-logic-by-using-six.moves-a.patch,
> coverage_notes.txt
>
>
> Users who operate in a Python 3 environment may have trouble launching cqlsh.
> Could we please update cqlsh's syntax to run in Python 3?
> As a workaround, users can setup pyenv, and cd to a directory with a
> .python-version containing "2.7". But it would be nice if cqlsh supported
> modern Python versions out of the box.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-10190) Python 3 support for cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945585#comment-16945585
]
Andy Tolbert commented on CASSANDRA-10190:
--
Hi [~ptbannister], this is much needed and great work! I took a look at your
branch today and it looks really good to me. I have some minor suggestions, but
I think things are pretty good as is!
I made patches of my suggestions below ([^0001-Update-six-to-1.12.0.patch],
[^0002-Simplify-version-specific-logic-by-using-six.moves-a.patch]). Note that
other than the import change in {{winpty.py}}, these changes don't really fix
anything, so I would not mind if you chose not to accept them.
Recommended changes:
{{six}}
* I realized that a very old version of six (1.7.3) is being provided via lib
as the cassandra-driver being pulled in claims to require six 1.9.0. We should
consider upgrading that, especially since there are some newer features
(covered below) that may be useful.
* There are some additional features of six that could be used which would
simplify/remove python version checking logic. For example, there's a lot of
code that calls encode/decode if PY2 is used, {{six.ensure_text}} could be used
instead.
{{bin/cqlsh}}
* L85-95: Commented out code probably not needed anymore?
{{bin/cqlsh.py}}
* L50-56: Could make use of
[six.moves|https://six.readthedocs.io/#module-six.moves] to impor in a
version-agnostic way, i.e. from {{six.moves import configparser}}, {{from
six.moves import cStringIO as StringIO}})
* L867: Instead of {{_input}}, could use {{six.moves.input}}.
{{pylib/copyutil.py}}
* L48-54: use {{six.moves}} (see comment ^ {{cqlsh.py}})
* where {{range}} is used in favor of {{xrange}}, it would be good to use
{{six.moves.range}} instead, since when using python2 {{xrange}} will be used
so the existing behavior for python2 will be maintained.
{{pylib/cqlshlib/formatting.py}}
* {{ensure_text}} can be utilized in a places to simplify conversion logic.
{{pylib/cqlshlib/saferscanner.py}}
* Unless i'm mistaken {{Py35SaferScanner}} and {{Py36SaferScanner}} are the
same, {{Py35SaferScanner}} not used, so can be removed.
{{pylib/cqlshlib/sslhandling.py}}
* L21-24, use {{six.moves}}
{{pylib/cqlshlib/test/winpty.py}} & {{pylib/cqlshlib/util.py}}
* import queue won't work with python2, & might as well use cStringIO
The tests all passed for me except the one you mentioned with python3
(TestCqlshOutput#test_user_types). I’m pretty certain this is fixed in newer
python driver versions. The driver bundled with C* is several minor versions
old and is an internal build with some changes for transient replicas (I’m
guessing has to do with the way you express replication when creating a
keyspace with transient replicas). I think it's worth updating the driver to a
newer version, and maybe that can be done in a separate patch unless you think
it should be done here?
> Python 3 support for cqlsh
> --
>
> Key: CASSANDRA-10190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10190
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
>Reporter: Andrew Pennebaker
>Assignee: Patrick Bannister
>Priority: Normal
> Labels: cqlsh
> Fix For: 4.0, 4.0-alpha
>
> Attachments: 0001-Update-six-to-1.12.0.patch,
> 0002-Simplify-version-specific-logic-by-using-six.moves-a.patch,
> coverage_notes.txt
>
>
> Users who operate in a Python 3 environment may have trouble launching cqlsh.
> Could we please update cqlsh's syntax to run in Python 3?
> As a workaround, users can setup pyenv, and cd to a directory with a
> .python-version containing "2.7". But it would be nice if cqlsh supported
> modern Python versions out of the box.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-10190) Python 3 support for cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Tolbert updated CASSANDRA-10190: - Attachment: 0002-Simplify-version-specific-logic-by-using-six.moves-a.patch 0001-Update-six-to-1.12.0.patch > Python 3 support for cqlsh > -- > > Key: CASSANDRA-10190 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10190 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Tools >Reporter: Andrew Pennebaker >Assignee: Patrick Bannister >Priority: Normal > Labels: cqlsh > Fix For: 4.0, 4.0-alpha > > Attachments: 0001-Update-six-to-1.12.0.patch, > 0002-Simplify-version-specific-logic-by-using-six.moves-a.patch, > coverage_notes.txt > > > Users who operate in a Python 3 environment may have trouble launching cqlsh. > Could we please update cqlsh's syntax to run in Python 3? > As a workaround, users can setup pyenv, and cd to a directory with a > .python-version containing "2.7". But it would be nice if cqlsh supported > modern Python versions out of the box. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15344) "tablestats" should be used instead of "cfstats"
DeepakVohra created CASSANDRA-15344: --- Summary: "tablestats" should be used instead of "cfstats" Key: CASSANDRA-15344 URL: https://issues.apache.org/jira/browse/CASSANDRA-15344 Project: Cassandra Issue Type: Bug Reporter: DeepakVohra As _nodetool cfstats_ has been renamed/aliased to _nodetool tablestats_ should CASSANDRA-13889 be referring to _cfstats_? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15196) Refactor inheritance around CommitLogSegment management and allocation
[ https://issues.apache.org/jira/browse/CASSANDRA-15196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie reassigned CASSANDRA-15196: - Assignee: Josh McKenzie (was: Joshua McKenzie) > Refactor inheritance around CommitLogSegment management and allocation > -- > > Key: CASSANDRA-15196 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15196 > Project: Cassandra > Issue Type: Improvement > Components: Local/Commit Log >Reporter: Joshua McKenzie >Assignee: Josh McKenzie >Priority: Normal > > Back when I wrote CASSANDRA-8844 and CASSANDRA-12148, a few things about the > CommitLog stood out to me that I wasn't in love with. At the time I was much > more of the mind of "When in Rome..." regarding some of our structures, our > naming, and specifically regarding our penchant for inheritance vs. > composition. Turns out I have an itch here I need to scratch. > This patch refactors the CommitLog in a few key ways: > * Removes inheritence for CommitLogSegmentManagerX, instead has a single > CommitLogSegmentManager and a CommitLogSegmentAllocator interface > ** This interface is implemented by CommitLogSegmentAllocatorStandard and > CommitLogSegmentAllocatorCDC > * Renames a few variables and methods within the segment manager to make > their purpose and role more clear from names alone (hopefully): > ** allocatingFrom --> activeSegment > ** allocatingFrom() --> getActiveSegment() > ** advanceAllocatingFrom() – switchToNewSegment() > ** activeSegments --> unflushedSegments > ** getActiveSegments --> getUnflushedSegments() > ** awaitAvailableSegment(...) --> awaitSegmentAllocation(...) > ** isStillAllocating() --> hasRoom() > * Reorders some of the "allocation-and-compare-in-while-loop-decl) to more > idiomatic style > * Adds some comments to various under-documented methods, mostly related to > CDC and timing > As far as we are in the 4.0 testing, I don't expect this to hit pre 4.0. > Given it's a relatively minor refactor in well-tested code, doesn't change > functionality, and doesn't impact any of the publicly exposed APIs in the > CommitLog ecosystem, I'd be comfortable with it going in a minor release > after 4.0 is out. But I'm open to alternative viewpoints. > Have run unit tests locally w/out issue on both regular and cdc-targets; need > to get CI against the branch internally for full dtest run and I'll post when > it's done. Just wanted to get visibility to this out there in case anyone was > curious or thinking of working on the same thing. > [ Link to branch on > github|https://github.com/apache/cassandra/compare/trunk...josh-mckenzie:clean_cl_comp] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-13085) Cassandra fails to start because WindowsFailedSnapshotTracker can not write to CASSANDRA_HOME
[
https://issues.apache.org/jira/browse/CASSANDRA-13085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie reassigned CASSANDRA-13085:
-
Assignee: Josh McKenzie (was: Joshua McKenzie)
> Cassandra fails to start because WindowsFailedSnapshotTracker can not write
> to CASSANDRA_HOME
> -
>
> Key: CASSANDRA-13085
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13085
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths, Packaging
> Environment: might be windows only considering the classname
>Reporter: Pieter-Jan Pintens
>Assignee: Josh McKenzie
>Priority: Normal
> Labels: windows
>
> We are currently trying to package Cassandra with our application.
> In windows our server does not want to start because it want to write to
> CASSANDRA_HOME\.toDelete, since we install to 'C:\program files\...' this is
> not possible when started under a non privileged user. We were hoping that
> setting pointers for the data and log dir to a writable location (somewhere
> under user home) would be enough to start cassandra but this component wants
> to write to a path that we cannot modify.
> For us there are a couple of solutions:
> 1) the location can be specified using a system property like data and log
> dirs
> 2) this file is written to the data location
> Our current work arround would be to patch this class file but that is hard
> to maintain.
> {noformat}
> Exception (java.lang.RuntimeException) encountered during startup: Failed to
> cre
> ate failed snapshot tracking file [.toDelete]. Aborting
> java.lang.RuntimeException: Failed to create failed snapshot tracking file
> [.toDelete]. Aborting
> at
> org.apache.cassandra.db.WindowsFailedSnapshotTracker.deleteOldSnapshots(WindowsFailedSnapshotTracker.java:98)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:186)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:601)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:730)
> at com.id.cassandra.wrapper.Main.main(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-11575) Add out-of-process testing for CDC
[ https://issues.apache.org/jira/browse/CASSANDRA-11575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie reassigned CASSANDRA-11575: - Assignee: Josh McKenzie (was: Joshua McKenzie) > Add out-of-process testing for CDC > -- > > Key: CASSANDRA-11575 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11575 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Testing >Reporter: Carl Yeksigian >Assignee: Josh McKenzie >Priority: Normal > Fix For: 4.x > > Attachments: 11575.tgz, 11575.tgz > > > There are currently no dtests for the new cdc feature. We should have some, > at least to ensure that the cdc files have a lifecycle that makes sense, and > make sure that things like a continually cleaning daemon and a lazy daemon > have the properties we expect; for this, we don't need to actually process > the files, but make sure they fit the characteristics we expect from them. A > more complex daemon would need to be written in Java. > I already hit a problem where if the cdc is over capacity, the cdc properly > throws the WTE, but it will not reset after the overflow directory is > undersize again. It is supposed to correct the size within 250ms and allow > more writes. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15046) Add a "history" command to cqlsh. Perhaps "show history"?
[ https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Kumar reassigned CASSANDRA-15046: --- Assignee: Rohit Kumar > Add a "history" command to cqlsh. Perhaps "show history"? > -- > > Key: CASSANDRA-15046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15046 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Wes Peters >Assignee: Rohit Kumar >Priority: Low > Labels: lhf > > I was trying to capture some create key space and create table commands from > a running cqlsh, and found there was no equivalent to the '\s' history > command in Postgres' psql shell. It's a great tool for figuring out what you > were doing yesterday. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15046) Add a "history" command to cqlsh. Perhaps "show history"?
[ https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945372#comment-16945372 ] Rohit Kumar commented on CASSANDRA-15046: - Can I start working on this issue ? I am new to contributing to apache cassandra. > Add a "history" command to cqlsh. Perhaps "show history"? > -- > > Key: CASSANDRA-15046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15046 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Wes Peters >Priority: Low > Labels: lhf > > I was trying to capture some create key space and create table commands from > a running cqlsh, and found there was no equivalent to the '\s' history > command in Postgres' psql shell. It's a great tool for figuring out what you > were doing yesterday. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15046) Add a "history" command to cqlsh. Perhaps "show history"?
[ https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Kumar reassigned CASSANDRA-15046: --- Assignee: (was: Rohit Kumar) > Add a "history" command to cqlsh. Perhaps "show history"? > -- > > Key: CASSANDRA-15046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15046 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Wes Peters >Priority: Low > Labels: lhf > > I was trying to capture some create key space and create table commands from > a running cqlsh, and found there was no equivalent to the '\s' history > command in Postgres' psql shell. It's a great tool for figuring out what you > were doing yesterday. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15046) Add a "history" command to cqlsh. Perhaps "show history"?
[ https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Kumar reassigned CASSANDRA-15046: --- Assignee: Rohit Kumar > Add a "history" command to cqlsh. Perhaps "show history"? > -- > > Key: CASSANDRA-15046 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15046 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Wes Peters >Assignee: Rohit Kumar >Priority: Low > Labels: lhf > > I was trying to capture some create key space and create table commands from > a running cqlsh, and found there was no equivalent to the '\s' history > command in Postgres' psql shell. It's a great tool for figuring out what you > were doing yesterday. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15343) Java internal exception on empty partition key range and conditions
Konstantin created CASSANDRA-15343:
--
Summary: Java internal exception on empty partition key range and
conditions
Key: CASSANDRA-15343
URL: https://issues.apache.org/jira/browse/CASSANDRA-15343
Project: Cassandra
Issue Type: Bug
Components: CQL/Semantics
Reporter: Konstantin
sandra@cqlsh> create keyspace test with replication = \{ 'class':
'SimpleStrategy', 'replication_factor': 1} and DURABLE_WRITES=true ;
cassandra@cqlsh> use test;
cassandra@cqlsh:test> create table lwt (a int primary key, b int);
cassandra@cqlsh:test> update lwt set b = 1 where a = 1 and token(a) > 0 and
token(a)< 0;
cassandra@cqlsh:test> update lwt set b = 1 where a = 1 and token(a) > 0 and
token(a)< 0 if b = 1;
ServerError: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
