[jira] [Commented] (CASSANDRA-12622) Snap package of Cassandra
[
https://issues.apache.org/jira/browse/CASSANDRA-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935598#comment-15935598
]
Murukesh Mohanan commented on CASSANDRA-12622:
--
I had a go at reviewing this, and there is a major problem: {{snapcraft
cleanbuild}} doesn't build this snap cleanly:
{code}
Copying needed target link from the system /etc/ssl/certs/java/cacerts
Pulling cassandra
Cloning into '/root/parts/cassandra/src'...
done.
Preparing to pull glue
Pulling glue
Preparing to build cassandra
Building cassandra
Buildfile: /root/parts/cassandra/build/build.xml
BUILD FAILED
/root/parts/cassandra/build/build.xml:1051: taskdef A class needed by class
org.krummas.junit.JStackJUnitTask cannot be found:
org/apache/tools/ant/taskdefs/optional/junit/JUnitTask
using the classloader
AntClassLoader[/root/parts/cassandra/build/lib/jstackjunit-0.0.1.jar]
Total time: 1 second
Command '['/bin/sh', '/tmp/tmpmfqzqafe', 'ant', 'artifacts',
'-Ddist.dir=/root/parts/cassandra/install']' returned non-zero exit status 1
ant artifacts -Ddist.dir=/root/parts/cassandra/install
Command '['lxc', 'exec', 'snapcraft-yearly-finer-glider', '--', 'snapcraft',
'snap', '--output', 'cassandra_3.10-SNAPSHOT_amd64.snap']' returned non-zero
exit status 1
Stopping snapcraft-yearly-finer-glider
{code}
Now, a plain {{snapcraft}} works, but I had problems with locale [1], but IMHO
from a package maintenance perspective, if a {{cleanbuild}} fails, then the
packaging configuration has problems.
[1]: I was working with {{LC_ALL=C}}, and that causes {{javadoc}} to fail if it
finds Unicode characters in files. I had to use {{LC_ALL=C.UTF-8}} before the
snap built. But, in any case, while building packages a clean-room environment
should be used, and it shouldn't be affected my personal quirky settings.
> Snap package of Cassandra
> -
>
> Key: CASSANDRA-12622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12622
> Project: Cassandra
> Issue Type: New Feature
> Components: Packaging
>Reporter: Evan
>Priority: Minor
> Fix For: 3.11.x
>
>
> Picking up the conversation from [1], I'd like to propose that Cassandra
> publish snap packages (http://snapcraft.io).
> I've put together a patch:
> https://github.com/apache/cassandra/compare/trunk...evandandrea:snap
> This could be used to build and publish a snap on every commit to trunk [2,
> 3], or as a quicker way for developers to one-off build something more
> lightweight than a container for testing.
> Alternatively, you could keep snap publication to released versions of
> Cassandra. Dependencies are bundled, so you would get to decide Oracle vs
> OpenJDK and the exact version. For the end user it would mean confidence that
> Cassandra with this bundled set of dependencies had been tested by the
> project. Uploads would instantly reach all of Ubuntu and a fair few other
> distributions without any changes [4], hopefully simplifying install
> instructions.
> I couldn't find where the machinery for driving the Cassandra release process
> lives, but if someone can point me in the right direction I'd be happy to
> submit a patch for that.
> 1: https://www.mail-archive.com/dev@cassandra.apache.org/msg09216.html
> 2: Builds of trunk would be best published to the edge channel:
> http://snapcraft.io/#snapcraft_home_using-snaps_channels
> 3: What automatic building and publishing could look like using Travis:
> https://travis-ci.org/evandandrea/cassandra-snap/builds/158449135#L3937
> 4: http://snapcraft.io/docs/core/install
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CASSANDRA-12988) make the consistency level for user-level auth reads and writes configurable
[
https://issues.apache.org/jira/browse/CASSANDRA-12988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Jirsa updated CASSANDRA-12988:
---
Fix Version/s: 4.x
> make the consistency level for user-level auth reads and writes configurable
>
>
> Key: CASSANDRA-12988
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12988
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
>Reporter: Jason Brown
>Assignee: Jason Brown
>Priority: Minor
> Fix For: 4.x
>
>
> Most reads for the auth-related tables execute at {{LOCAL_ONE}}. We'd like to
> make it configurable, with the default still being {{LOCAL_ONE}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935543#comment-15935543 ] Robert Stupp commented on CASSANDRA-13360: -- Yep - will do that this week. > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt, 13360-trunk.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935539#comment-15935539 ] Jay Zhuang commented on CASSANDRA-13360: Update the [patch|https://github.com/apache/cassandra/compare/trunk...cooldoger:13360-trunk] for trunk. Passed the utest locally. Could someone please submit the [patch|https://github.com/apache/cassandra/compare/trunk...cooldoger:13360-trunk] to CI? > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt, 13360-trunk.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935528#comment-15935528 ] Dave Brosius commented on CASSANDRA-13360: -- Going to Junit 4.11 introduces hash code ordering of tests. Certainly a good idea, but one that can show dependency problems, that you didn't expect. Just FYI > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt, 13360-trunk.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
cassandra-builds git commit: Add note to allow sudo NOPASSWD or provide pass
Repository: cassandra-builds Updated Branches: refs/heads/master 864e57095 -> dc96c0476 Add note to allow sudo NOPASSWD or provide pass Project: http://git-wip-us.apache.org/repos/asf/cassandra-builds/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra-builds/commit/dc96c047 Tree: http://git-wip-us.apache.org/repos/asf/cassandra-builds/tree/dc96c047 Diff: http://git-wip-us.apache.org/repos/asf/cassandra-builds/diff/dc96c047 Branch: refs/heads/master Commit: dc96c0476487ca58ba38ae115f4459b4fa0d5c9b Parents: 864e570 Author: Michael Shuler Authored: Tue Mar 21 18:01:43 2017 -0500 Committer: Michael Shuler Committed: Tue Mar 21 18:01:43 2017 -0500 -- ASF-slaves.txt | 4 1 file changed, 4 insertions(+) -- http://git-wip-us.apache.org/repos/asf/cassandra-builds/blob/dc96c047/ASF-slaves.txt -- diff --git a/ASF-slaves.txt b/ASF-slaves.txt index a90230b..15cadc5 100644 --- a/ASF-slaves.txt +++ b/ASF-slaves.txt @@ -10,6 +10,10 @@ with only their default installation of bind9 removed: $ sudo apt-get autoremove --purge bind9 $ sudo rm -r /var/cache/bind +Edit sudoers to allow INFRA to sudo without password, or provide them with the password. +For example, set: %sudo ALL=(ALL:ALL) NOPASSWD:ALL + $ sudo visudo + Add jenkins user: $ sudo useradd -m -s /bin/bash jenkins
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-13360: - Reviewer: Robert Stupp > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt, 13360-trunk.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Zhuang updated CASSANDRA-13360: --- Status: Patch Available (was: Open) > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt, 13360-trunk.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Zhuang updated CASSANDRA-13360: --- Attachment: 13360-trunk.txt > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt, 13360-trunk.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-12773) cassandra-stress error for one way SSL
[
https://issues.apache.org/jira/browse/CASSANDRA-12773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Jirsa updated CASSANDRA-12773:
---
Status: Patch Available (was: Open)
> cassandra-stress error for one way SSL
> ---
>
> Key: CASSANDRA-12773
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12773
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Jane Deng
>Assignee: Stefan Podkowinski
> Fix For: 2.2.x
>
> Attachments: 12773-2.2.patch
>
>
> CASSANDRA-9325 added keystore/truststore configuration into cassandra-stress.
> However, for one way ssl (require_client_auth=false), there is no need to
> pass keystore info into ssloptions. Cassadra-stress errored out:
> {noformat}
> java.lang.RuntimeException: java.io.IOException: Error creating the
> initializing the SSL Context
> at
> org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:200)
>
> at
> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpacesNative(SettingsSchema.java:79)
>
> at
> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:69)
>
> at
> org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:207)
>
> at org.apache.cassandra.stress.StressAction.run(StressAction.java:55)
> at org.apache.cassandra.stress.Stress.main(Stress.java:117)
> Caused by: java.io.IOException: Error creating the initializing the SSL
> Context
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:151)
>
> at
> org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:128)
>
> at
> org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:191)
>
> ... 5 more
> Caused by: java.io.IOException: Keystore was tampered with, or password was
> incorrect
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:772)
> at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55)
> at java.security.KeyStore.load(KeyStore.java:1445)
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:129)
>
> ... 7 more
> Caused by: java.security.UnrecoverableKeyException: Password verification
> failed
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:770)
> ... 10 more
> {noformat}
> It's a bug from CASSANDRA-9325. When the keystore is absent, the keystore is
> assigned to the path of the truststore, but the password isn't taken care.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
cassandra-builds git commit: Fix jenkins user's ssh key addition
Repository: cassandra-builds Updated Branches: refs/heads/master 4253406d9 -> 864e57095 Fix jenkins user's ssh key addition Project: http://git-wip-us.apache.org/repos/asf/cassandra-builds/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra-builds/commit/864e5709 Tree: http://git-wip-us.apache.org/repos/asf/cassandra-builds/tree/864e5709 Diff: http://git-wip-us.apache.org/repos/asf/cassandra-builds/diff/864e5709 Branch: refs/heads/master Commit: 864e57095d3de59fa370a2d9ce31b618e6915a9c Parents: 4253406 Author: Michael Shuler Authored: Tue Mar 21 17:37:37 2017 -0500 Committer: Michael Shuler Committed: Tue Mar 21 17:37:37 2017 -0500 -- ASF-slaves.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra-builds/blob/864e5709/ASF-slaves.txt -- diff --git a/ASF-slaves.txt b/ASF-slaves.txt index a489bdb..a90230b 100644 --- a/ASF-slaves.txt +++ b/ASF-slaves.txt @@ -16,7 +16,7 @@ Add jenkins user: Add ssh pub key from puppet deployment repo: https://github.com/apache/infrastructure-puppet/blob/deployment/data/ubuntu/1404.yaml#L295 $ sudo mkdir /home/jenkins/.ssh - $ sudo sh -c "echo 'B3NzaC1yc2EBIwAAAIEAtxkcKDiPh1OaVzaVdc80daKq2sRy8aAgt8u2uEcLClzMrnv/g19db7XVggfT4+HPCqcbFbO3mtVnUnWWtuSEpDjqriWnEcSj2G1P53zsdKEu9qCGLmEFMgwcq8b5plv78PRdAQn09WCBI1QrNMypjxgCKhNNn45WqV4AD8Jp7/8=' > /home/jenkins/.ssh/authorized_keys" + $ sudo sh -c "echo 'ssh-rsa B3NzaC1yc2EBIwAAAIEAtxkcKDiPh1OaVzaVdc80daKq2sRy8aAgt8u2uEcLClzMrnv/g19db7XVggfT4+HPCqcbFbO3mtVnUnWWtuSEpDjqriWnEcSj2G1P53zsdKEu9qCGLmEFMgwcq8b5plv78PRdAQn09WCBI1QrNMypjxgCKhNNn45WqV4AD8Jp7/8=' > /home/jenkins/.ssh/authorized_keys" $ sudo chown -R jenkins:jenkins /home/jenkins/.ssh $ sudo chmod 700 /home/jenkins/.ssh $ sudo chmod 600 /home/jenkins/.ssh/authorized_keys
[jira] [Commented] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935476#comment-15935476 ] Jeff Jirsa commented on CASSANDRA-13360: junit seems like one of the lowest risk pieces, but also agree that this should be trunk/4.0 only. > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-12773) cassandra-stress error for one way SSL
[
https://issues.apache.org/jira/browse/CASSANDRA-12773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935449#comment-15935449
]
Robert Stupp commented on CASSANDRA-12773:
--
Missed your update, [~spod], it's not "patch available".
Can you submit the tests for trunk?
(There's something wrong with the links you added - found the results for 2.3,
3.0, 3.11.)
> cassandra-stress error for one way SSL
> ---
>
> Key: CASSANDRA-12773
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12773
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Jane Deng
>Assignee: Stefan Podkowinski
> Fix For: 2.2.x
>
> Attachments: 12773-2.2.patch
>
>
> CASSANDRA-9325 added keystore/truststore configuration into cassandra-stress.
> However, for one way ssl (require_client_auth=false), there is no need to
> pass keystore info into ssloptions. Cassadra-stress errored out:
> {noformat}
> java.lang.RuntimeException: java.io.IOException: Error creating the
> initializing the SSL Context
> at
> org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:200)
>
> at
> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpacesNative(SettingsSchema.java:79)
>
> at
> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:69)
>
> at
> org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:207)
>
> at org.apache.cassandra.stress.StressAction.run(StressAction.java:55)
> at org.apache.cassandra.stress.Stress.main(Stress.java:117)
> Caused by: java.io.IOException: Error creating the initializing the SSL
> Context
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:151)
>
> at
> org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:128)
>
> at
> org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:191)
>
> ... 5 more
> Caused by: java.io.IOException: Keystore was tampered with, or password was
> incorrect
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:772)
> at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55)
> at java.security.KeyStore.load(KeyStore.java:1445)
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:129)
>
> ... 7 more
> Caused by: java.security.UnrecoverableKeyException: Password verification
> failed
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:770)
> ... 10 more
> {noformat}
> It's a bug from CASSANDRA-9325. When the keystore is absent, the keystore is
> assigned to the path of the truststore, but the password isn't taken care.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CASSANDRA-10383) Disable auto snapshot on selected tables.
[ https://issues.apache.org/jira/browse/CASSANDRA-10383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-10383: - Reviewer: (was: Robert Stupp) > Disable auto snapshot on selected tables. > - > > Key: CASSANDRA-10383 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10383 > Project: Cassandra > Issue Type: Improvement >Reporter: Tommy Stendahl >Assignee: Tommy Stendahl > Labels: doc-impacting, messaging-service-bump-required > Fix For: 4.x > > Attachments: 10383.txt > > > I have a use case where I would like to turn off auto snapshot for selected > tables, I don't want to turn it off completely since its a good feature. > Looking at the code I think it would be relatively easy to fix. > My plan is to create a new table property named something like > "disable_auto_snapshot". If set to false it will prevent auto snapshot on the > table, if set to true auto snapshot will be controlled by the "auto_snapshot" > property in the cassandra.yaml. Default would be true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-8720) Provide tools for finding wide row/partition keys
[ https://issues.apache.org/jira/browse/CASSANDRA-8720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-8720: Reviewer: (was: Robert Stupp) > Provide tools for finding wide row/partition keys > - > > Key: CASSANDRA-8720 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8720 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: J.B. Langston > Fix For: 2.1.x, 2.2.x > > Attachments: 8720.txt > > > Multiple users have requested some sort of tool to help identify wide row > keys. They get into a situation where they know a wide row/partition has been > inserted and it's causing problems for them but they have no idea what the > row key is in order to remove it. > Maintaining the widest row key currently encountered and displaying it in > cfstats would be one possible approach. > Another would be an offline tool (possibly an enhancement to sstablekeys) to > show the number of columns/bytes per key in each sstable. If a tool to > aggregate the information at a CF-level could be provided that would be a > bonus, but it shouldn't be too hard to write a script wrapper to aggregate > them if not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-11537) Give clear error when certain nodetool commands are issued before server is ready
[
https://issues.apache.org/jira/browse/CASSANDRA-11537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-11537:
-
Reviewer: (was: Robert Stupp)
> Give clear error when certain nodetool commands are issued before server is
> ready
> -
>
> Key: CASSANDRA-11537
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11537
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Edward Capriolo
>Assignee: Edward Capriolo
>Priority: Minor
> Labels: lhf
>
> As an ops person upgrading and servicing Cassandra servers, I require a more
> clear message when I issue a nodetool command that the server is not ready
> for it so that I am not confused.
> Technical description:
> If you deploy a new binary, restart, and issue nodetool
> scrub/compact/updatess etc you get unfriendly assertion. An exception would
> be easier to understand. Also if a user has turned assertions off it is
> unclear what might happen.
> {noformat}
> EC1: Throw exception to make it clear server is still in start up process.
> :~# nodetool upgradesstables
> error: null
> -- StackTrace --
> java.lang.AssertionError
> at org.apache.cassandra.db.Keyspace.open(Keyspace.java:97)
> at
> org.apache.cassandra.service.StorageService.getValidKeyspace(StorageService.java:2573)
> at
> org.apache.cassandra.service.StorageService.getValidColumnFamilies(StorageService.java:2661)
> at
> org.apache.cassandra.service.StorageService.upgradeSSTables(StorageService.java:2421)
> {noformat}
> EC1:
> Patch against 2.1 (branch)
> https://github.com/apache/cassandra/compare/trunk...edwardcapriolo:exception-on-startup?expand=1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935438#comment-15935438 ] Robert Stupp commented on CASSANDRA-13360: -- Mean, we should be very careful with such changes. > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-13360: - Status: Open (was: Patch Available) > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-13360: - Priority: Minor (was: Major) Fix Version/s: (was: 3.0.x) 4.x We usually do not update libraries unless there are bugs in stable branches. Since this is not a bug fix, updating fix version to 4.x. > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Minor > Labels: test > Fix For: 4.x > > Attachments: 13360-3.0.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935428#comment-15935428 ] Jay Zhuang commented on CASSANDRA-13360: utest is passed locally for 3.0 branch. Running tests on 3.11 and trunk. > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang > Labels: test > Fix For: 3.0.x > > Attachments: 13360-3.0.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Zhuang updated CASSANDRA-13360: --- Fix Version/s: 3.0.x Status: Patch Available (was: Open) > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang > Labels: test > Fix For: 3.0.x > > Attachments: 13360-3.0.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Zhuang updated CASSANDRA-13360: --- Attachment: 13360-3.0.txt > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang > Labels: test > Attachments: 13360-3.0.txt > > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13336) Upgrade the snappy-java version to 1.1.2.x
[ https://issues.apache.org/jira/browse/CASSANDRA-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13336: --- Component/s: (was: Configuration) Libraries > Upgrade the snappy-java version to 1.1.2.x > -- > > Key: CASSANDRA-13336 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13336 > Project: Cassandra > Issue Type: Improvement > Components: Libraries >Reporter: yuqi >Assignee: Jeff Jirsa > Fix For: 4.x > > > Snappy-java added support for AArch64 since version > 1.1.2.x.(https://github.com/xerial/snappy-java/pull/135). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13360: --- Component/s: Libraries > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Libraries, Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang > Labels: test > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13361) Consider upgrading bundled libraries to modern versions
[ https://issues.apache.org/jira/browse/CASSANDRA-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13361: --- Component/s: Libraries > Consider upgrading bundled libraries to modern versions > --- > > Key: CASSANDRA-13361 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13361 > Project: Cassandra > Issue Type: Improvement > Components: Libraries >Reporter: Jeff Jirsa >Assignee: Jeff Jirsa > Fix For: 4.x > > > Creating umbrella for all of the "upgrade to modern version" tickets, > with 4.0 coming up, seems like a good time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CASSANDRA-13361) Consider upgrading bundled libraries to modern versions
[ https://issues.apache.org/jira/browse/CASSANDRA-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa reassigned CASSANDRA-13361: -- Assignee: Jeff Jirsa > Consider upgrading bundled libraries to modern versions > --- > > Key: CASSANDRA-13361 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13361 > Project: Cassandra > Issue Type: Improvement > Components: Libraries >Reporter: Jeff Jirsa >Assignee: Jeff Jirsa > Fix For: 4.x > > > Creating umbrella for all of the "upgrade to modern version" tickets, > with 4.0 coming up, seems like a good time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CASSANDRA-13361) Consider upgrading bundled libraries to modern versions
Jeff Jirsa created CASSANDRA-13361: -- Summary: Consider upgrading bundled libraries to modern versions Key: CASSANDRA-13361 URL: https://issues.apache.org/jira/browse/CASSANDRA-13361 Project: Cassandra Issue Type: Improvement Reporter: Jeff Jirsa Fix For: 4.x Creating umbrella for all of the "upgrade to modern version" tickets, with 4.0 coming up, seems like a good time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
[ https://issues.apache.org/jira/browse/CASSANDRA-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Zhuang updated CASSANDRA-13360: --- Description: Current stable release is 4.12: [released in 2014|https://github.com/junit-team/junit4/releases]. We can levege more test features like Rule, TemporaryFolder, Parameterized Tests, Theories, etc. Here are the release notes: https://github.com/junit-team/junit4/tree/master/doc Junit-4.6 is a very old version [released in 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. was: Current stable release is 4.12, released in [2014|https://github.com/junit-team/junit4/releases]. We can levege more test features like Rule, TemporaryFolder, Parameterized Tests, Theories, etc. Here are the release notes: https://github.com/junit-team/junit4/tree/master/doc Junit-4.6 is a very old version [released in 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. > Upgrade junit from 4.6 to 4.12 > -- > > Key: CASSANDRA-13360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 > Project: Cassandra > Issue Type: Improvement > Components: Testing >Reporter: Jay Zhuang >Assignee: Jay Zhuang > Labels: test > > Current stable release is 4.12: [released in > 2014|https://github.com/junit-team/junit4/releases]. > We can levege more test features like Rule, TemporaryFolder, Parameterized > Tests, Theories, etc. Here are the release notes: > https://github.com/junit-team/junit4/tree/master/doc > Junit-4.6 is a very old version [released in > 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CASSANDRA-13360) Upgrade junit from 4.6 to 4.12
Jay Zhuang created CASSANDRA-13360: -- Summary: Upgrade junit from 4.6 to 4.12 Key: CASSANDRA-13360 URL: https://issues.apache.org/jira/browse/CASSANDRA-13360 Project: Cassandra Issue Type: Improvement Components: Testing Reporter: Jay Zhuang Assignee: Jay Zhuang Current stable release is 4.12, released in [2014|https://github.com/junit-team/junit4/releases]. We can levege more test features like Rule, TemporaryFolder, Parameterized Tests, Theories, etc. Here are the release notes: https://github.com/junit-team/junit4/tree/master/doc Junit-4.6 is a very old version [released in 2009|https://github.com/junit-team/junit4/releases?after=r4.7]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13308) Gossip breaks, Hint files not being deleted on nodetool decommission
[ https://issues.apache.org/jira/browse/CASSANDRA-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Jirsa updated CASSANDRA-13308: --- Fix Version/s: 4.x 3.11.x 3.0.x > Gossip breaks, Hint files not being deleted on nodetool decommission > > > Key: CASSANDRA-13308 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13308 > Project: Cassandra > Issue Type: Bug > Components: Streaming and Messaging > Environment: Using Cassandra version 3.0.9 >Reporter: Arijit >Assignee: Jeff Jirsa > Fix For: 3.0.x, 3.11.x, 4.x > > Attachments: 28207.stack, logs, logs_decommissioned_node > > > How to reproduce the issue I'm seeing: > Shut down Cassandra on one node of the cluster and wait until we accumulate a > ton of hints. Start Cassandra on the node and immediately run "nodetool > decommission" on it. > The node streams its replicas and marks itself as DECOMMISSIONED, but other > nodes do not seem to see this message. "nodetool status" shows the > decommissioned node in state "UL" on all other nodes (it is also present in > system.peers), and Cassandra logs show that gossip tasks on nodes are not > proceeding (number of pending tasks keeps increasing). Jstack suggests that a > gossip task is blocked on hints dispatch (I can provide traces if this is not > obvious). Because the cluster is large and there are a lot of hints, this is > taking a while. > On inspecting "/var/lib/cassandra/hints" on the nodes, I see a bunch of hint > files for the decommissioned node. Documentation seems to suggest that these > hints should be deleted during "nodetool decommission", but it does not seem > to be the case here. This is the bug being reported. > To recover from this scenario, if I manually delete hint files on the nodes, > the hints dispatcher threads throw a bunch of exceptions and the > decommissioned node is now in state "DL" (perhaps it missed some gossip > messages?). The node is still in my "system.peers" table > Restarting Cassandra on all nodes after this step does not fix the issue (the > node remains in the peers table). In fact, after this point the > decommissioned node is in state "DN" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13333) Cassandra does not start on Windows due to 'JNA link failure'
[
https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935346#comment-15935346
]
Michael Kjellman commented on CASSANDRA-1:
--
[~blerer]
* Just chatted quickly with [~jasobrown] and [~jjirsa] and I think hiding the
fact we're using JNA under the hood and going with {{isAvailable()}} vs.
{{jnaAvailable()}] is a good change, however, I think that changes the scope a
bit. In the case of {{CLibraryWindows}} I used the existing Sigar based logic
to get the current PID of the running JVM as I wasn't sure if the *nix APIs
would work in Windows land. Thinking about it, this means {{isAvailable()}} is
a bit more nuanced. For instance, in the current {{CLibraryWindows}} case, yes,
the {{callGetpid()}} method is "available" but all the other methods that we
happen to have right now use JNA, which isn't "available" in the Windows case.
* Do you happen to know if the native {{getpid()}} JNA will work on Windows? If
so we can switch that from Sigar -> JNA for Windows too just like we're already
doing for the Linux/Darwin case. If so, it makes sense to attempt to load JNA
and libc in the WIndows case too?
* I don't think we should remove the checkJnaInitialization {{StartupCheck}} at
minimum in the Linux and Darwin cases. Given that we ship JNA in the release,
either we can't link against the library it due to an issue or someone removed
it. Given the performance implications I think we should leave the hard fail in
place -- but skip it if the current OS type is Windows.
> Cassandra does not start on Windows due to 'JNA link failure'
> -
>
> Key: CASSANDRA-1
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1
> Project: Cassandra
> Issue Type: Bug
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Blocker
>
> Cassandra 3.0 HEAD does not start on Windows. The only error in the logs is:
> {{ERROR 16:30:10 JNA failing to initialize properly.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CASSANDRA-13333) Cassandra does not start on Windows due to 'JNA link failure'
[
https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Jirsa reassigned CASSANDRA-1:
--
Assignee: Benjamin Lerer (was: Michael Kjellman)
Reviewer: Michael Kjellman
> Cassandra does not start on Windows due to 'JNA link failure'
> -
>
> Key: CASSANDRA-1
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1
> Project: Cassandra
> Issue Type: Bug
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Blocker
>
> Cassandra 3.0 HEAD does not start on Windows. The only error in the logs is:
> {{ERROR 16:30:10 JNA failing to initialize properly.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CASSANDRA-13333) Cassandra does not start on Windows due to 'JNA link failure'
[
https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Kjellman reassigned CASSANDRA-1:
Assignee: Michael Kjellman (was: Benjamin Lerer)
> Cassandra does not start on Windows due to 'JNA link failure'
> -
>
> Key: CASSANDRA-1
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1
> Project: Cassandra
> Issue Type: Bug
>Reporter: Benjamin Lerer
>Assignee: Michael Kjellman
>Priority: Blocker
>
> Cassandra 3.0 HEAD does not start on Windows. The only error in the logs is:
> {{ERROR 16:30:10 JNA failing to initialize properly.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-12962) SASI: Index are rebuilt on restart
[
https://issues.apache.org/jira/browse/CASSANDRA-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935179#comment-15935179
]
Alex Petrov commented on CASSANDRA-12962:
-
Thank you [~iksaif]!
Fun fact: I've attached the screenshot of how it looked on my screen :) I
apologise I didn't notice it right away but it was pretty hard to spot!
> SASI: Index are rebuilt on restart
> --
>
> Key: CASSANDRA-12962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12962
> Project: Cassandra
> Issue Type: Improvement
> Components: sasi
>Reporter: Corentin Chary
>Assignee: Alex Petrov
>Priority: Minor
> Fix For: 3.11.x
>
> Attachments: screenshot-1.png
>
>
> Apparently when cassandra any index that does not index a value in *every*
> live SSTable gets rebuild. The offending code can be found in the constructor
> of SASIIndex.
> You can easilly reproduce it:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE test.test (
> a text PRIMARY KEY,
> b text,
> c text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX test_b_idx ON test.test (b) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> CREATE CUSTOM INDEX test_c_idx ON test.test (c) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> INSERT INTO test.test (a, b) VALUES ('a', 'b');
> {code}
> Log (I added additional traces):
> {code}
> INFO [main] 2016-11-28 15:32:21,191 ColumnFamilyStore.java:406 -
> Initializing test.test
> DEBUG [SSTableBatchOpen:1] 2016-11-28 15:32:21,192 SSTableReader.java:505 -
> Opening
> /mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big
> (0.034KiB)
> DEBUG [main] 2016-11-28 15:32:21,194 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@2f661b1a[id=6b00489b-7010-396e-9348-9f32f5167f88,name=test_b_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=b}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> INFO [main] 2016-11-28 15:32:21,194 DataTracker.java:152 -
> SSTableIndex.open(column: b, minTerm: value, maxTerm: value, minKey: key,
> maxKey: key, sstable: BigTableReader(path='/mnt/ssd/tmp/data/data/test/test\
> -229e6380b57711e68407158fde22e121/mc-1-big-Data.db'))
> DEBUG [main] 2016-11-28 15:32:21,195 SASIIndex.java:129 - Rebuilding SASI
> Indexes: {}
> DEBUG [main] 2016-11-28 15:32:21,195 ColumnFamilyStore.java:895 - Enqueuing
> flush of IndexInfo: 0.386KiB (0%) on-heap, 0.000KiB (0%) off-heap
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:465 - Writing Memtable-IndexInfo@748981977(0.054KiB serialized
> bytes, 1 ops, 0%/0% of on/off-heap limit), flushed range = (min(-9223\
> 372036854775808), max(9223372036854775807)]
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:494 - Completed flushing
> /mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db
> (0.035KiB) for\
> commitlog position CommitLogPosition(segmentId=1480343535479, position=15652)
> DEBUG [MemtableFlushWriter:1] 2016-11-28 15:32:21,224
> ColumnFamilyStore.java:1200 - Flushed to
> [BigTableReader(path='/mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db\
> ')] (1 sstables, 4.838KiB), biggest 4.838KiB, smallest 4.838KiB
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@12f3d291[id=45fcb286-b87a-3d18-a04b-b899a9880c91,name=test_c_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=c}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:121 - to rebuild: index:
> BigTableReader(path='/mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big-Data.db'),
> sstable: org.apache.cassa\
> nd
[jira] [Updated] (CASSANDRA-12962) SASI: Index are rebuilt on restart
[
https://issues.apache.org/jira/browse/CASSANDRA-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-12962:
Attachment: screenshot-1.png
> SASI: Index are rebuilt on restart
> --
>
> Key: CASSANDRA-12962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12962
> Project: Cassandra
> Issue Type: Improvement
> Components: sasi
>Reporter: Corentin Chary
>Assignee: Alex Petrov
>Priority: Minor
> Fix For: 3.11.x
>
> Attachments: screenshot-1.png
>
>
> Apparently when cassandra any index that does not index a value in *every*
> live SSTable gets rebuild. The offending code can be found in the constructor
> of SASIIndex.
> You can easilly reproduce it:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE test.test (
> a text PRIMARY KEY,
> b text,
> c text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX test_b_idx ON test.test (b) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> CREATE CUSTOM INDEX test_c_idx ON test.test (c) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> INSERT INTO test.test (a, b) VALUES ('a', 'b');
> {code}
> Log (I added additional traces):
> {code}
> INFO [main] 2016-11-28 15:32:21,191 ColumnFamilyStore.java:406 -
> Initializing test.test
> DEBUG [SSTableBatchOpen:1] 2016-11-28 15:32:21,192 SSTableReader.java:505 -
> Opening
> /mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big
> (0.034KiB)
> DEBUG [main] 2016-11-28 15:32:21,194 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@2f661b1a[id=6b00489b-7010-396e-9348-9f32f5167f88,name=test_b_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=b}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> INFO [main] 2016-11-28 15:32:21,194 DataTracker.java:152 -
> SSTableIndex.open(column: b, minTerm: value, maxTerm: value, minKey: key,
> maxKey: key, sstable: BigTableReader(path='/mnt/ssd/tmp/data/data/test/test\
> -229e6380b57711e68407158fde22e121/mc-1-big-Data.db'))
> DEBUG [main] 2016-11-28 15:32:21,195 SASIIndex.java:129 - Rebuilding SASI
> Indexes: {}
> DEBUG [main] 2016-11-28 15:32:21,195 ColumnFamilyStore.java:895 - Enqueuing
> flush of IndexInfo: 0.386KiB (0%) on-heap, 0.000KiB (0%) off-heap
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:465 - Writing Memtable-IndexInfo@748981977(0.054KiB serialized
> bytes, 1 ops, 0%/0% of on/off-heap limit), flushed range = (min(-9223\
> 372036854775808), max(9223372036854775807)]
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:494 - Completed flushing
> /mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db
> (0.035KiB) for\
> commitlog position CommitLogPosition(segmentId=1480343535479, position=15652)
> DEBUG [MemtableFlushWriter:1] 2016-11-28 15:32:21,224
> ColumnFamilyStore.java:1200 - Flushed to
> [BigTableReader(path='/mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db\
> ')] (1 sstables, 4.838KiB), biggest 4.838KiB, smallest 4.838KiB
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@12f3d291[id=45fcb286-b87a-3d18-a04b-b899a9880c91,name=test_c_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=c}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:121 - to rebuild: index:
> BigTableReader(path='/mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big-Data.db'),
> sstable: org.apache.cassa\
> ndra.index.sasi.conf.ColumnIndex@6cbb6b0e
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:129 - Rebuilding SASI
> Indexes:
> {BigTableReader(path='/mnt/ssd/tmp/data/data/test/test-229e6380b5
[jira] [Assigned] (CASSANDRA-12962) SASI: Index are rebuilt on restart
[
https://issues.apache.org/jira/browse/CASSANDRA-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov reassigned CASSANDRA-12962:
---
Assignee: Alex Petrov
> SASI: Index are rebuilt on restart
> --
>
> Key: CASSANDRA-12962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12962
> Project: Cassandra
> Issue Type: Improvement
> Components: sasi
>Reporter: Corentin Chary
>Assignee: Alex Petrov
>Priority: Minor
> Fix For: 3.11.x
>
>
> Apparently when cassandra any index that does not index a value in *every*
> live SSTable gets rebuild. The offending code can be found in the constructor
> of SASIIndex.
> You can easilly reproduce it:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE test.test (
> a text PRIMARY KEY,
> b text,
> c text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX test_b_idx ON test.test (b) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> CREATE CUSTOM INDEX test_c_idx ON test.test (c) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> INSERT INTO test.test (a, b) VALUES ('a', 'b');
> {code}
> Log (I added additional traces):
> {code}
> INFO [main] 2016-11-28 15:32:21,191 ColumnFamilyStore.java:406 -
> Initializing test.test
> DEBUG [SSTableBatchOpen:1] 2016-11-28 15:32:21,192 SSTableReader.java:505 -
> Opening
> /mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big
> (0.034KiB)
> DEBUG [main] 2016-11-28 15:32:21,194 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@2f661b1a[id=6b00489b-7010-396e-9348-9f32f5167f88,name=test_b_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=b}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> INFO [main] 2016-11-28 15:32:21,194 DataTracker.java:152 -
> SSTableIndex.open(column: b, minTerm: value, maxTerm: value, minKey: key,
> maxKey: key, sstable: BigTableReader(path='/mnt/ssd/tmp/data/data/test/test\
> -229e6380b57711e68407158fde22e121/mc-1-big-Data.db'))
> DEBUG [main] 2016-11-28 15:32:21,195 SASIIndex.java:129 - Rebuilding SASI
> Indexes: {}
> DEBUG [main] 2016-11-28 15:32:21,195 ColumnFamilyStore.java:895 - Enqueuing
> flush of IndexInfo: 0.386KiB (0%) on-heap, 0.000KiB (0%) off-heap
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:465 - Writing Memtable-IndexInfo@748981977(0.054KiB serialized
> bytes, 1 ops, 0%/0% of on/off-heap limit), flushed range = (min(-9223\
> 372036854775808), max(9223372036854775807)]
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:494 - Completed flushing
> /mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db
> (0.035KiB) for\
> commitlog position CommitLogPosition(segmentId=1480343535479, position=15652)
> DEBUG [MemtableFlushWriter:1] 2016-11-28 15:32:21,224
> ColumnFamilyStore.java:1200 - Flushed to
> [BigTableReader(path='/mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db\
> ')] (1 sstables, 4.838KiB), biggest 4.838KiB, smallest 4.838KiB
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@12f3d291[id=45fcb286-b87a-3d18-a04b-b899a9880c91,name=test_c_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=c}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:121 - to rebuild: index:
> BigTableReader(path='/mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big-Data.db'),
> sstable: org.apache.cassa\
> ndra.index.sasi.conf.ColumnIndex@6cbb6b0e
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:129 - Rebuilding SASI
> Indexes:
> {BigTableReader(path='/mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big-Data.db')=
[jira] [Commented] (CASSANDRA-12962) SASI: Index are rebuilt on restart
[
https://issues.apache.org/jira/browse/CASSANDRA-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935171#comment-15935171
]
Corentin Chary commented on CASSANDRA-12962:
Alex: I do not expect to have time to work on that in the next weeks, so feel
free to take it :)
> SASI: Index are rebuilt on restart
> --
>
> Key: CASSANDRA-12962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12962
> Project: Cassandra
> Issue Type: Improvement
> Components: sasi
>Reporter: Corentin Chary
>Priority: Minor
> Fix For: 3.11.x
>
>
> Apparently when cassandra any index that does not index a value in *every*
> live SSTable gets rebuild. The offending code can be found in the constructor
> of SASIIndex.
> You can easilly reproduce it:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE test.test (
> a text PRIMARY KEY,
> b text,
> c text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX test_b_idx ON test.test (b) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> CREATE CUSTOM INDEX test_c_idx ON test.test (c) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> INSERT INTO test.test (a, b) VALUES ('a', 'b');
> {code}
> Log (I added additional traces):
> {code}
> INFO [main] 2016-11-28 15:32:21,191 ColumnFamilyStore.java:406 -
> Initializing test.test
> DEBUG [SSTableBatchOpen:1] 2016-11-28 15:32:21,192 SSTableReader.java:505 -
> Opening
> /mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big
> (0.034KiB)
> DEBUG [main] 2016-11-28 15:32:21,194 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@2f661b1a[id=6b00489b-7010-396e-9348-9f32f5167f88,name=test_b_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=b}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> INFO [main] 2016-11-28 15:32:21,194 DataTracker.java:152 -
> SSTableIndex.open(column: b, minTerm: value, maxTerm: value, minKey: key,
> maxKey: key, sstable: BigTableReader(path='/mnt/ssd/tmp/data/data/test/test\
> -229e6380b57711e68407158fde22e121/mc-1-big-Data.db'))
> DEBUG [main] 2016-11-28 15:32:21,195 SASIIndex.java:129 - Rebuilding SASI
> Indexes: {}
> DEBUG [main] 2016-11-28 15:32:21,195 ColumnFamilyStore.java:895 - Enqueuing
> flush of IndexInfo: 0.386KiB (0%) on-heap, 0.000KiB (0%) off-heap
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:465 - Writing Memtable-IndexInfo@748981977(0.054KiB serialized
> bytes, 1 ops, 0%/0% of on/off-heap limit), flushed range = (min(-9223\
> 372036854775808), max(9223372036854775807)]
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:494 - Completed flushing
> /mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db
> (0.035KiB) for\
> commitlog position CommitLogPosition(segmentId=1480343535479, position=15652)
> DEBUG [MemtableFlushWriter:1] 2016-11-28 15:32:21,224
> ColumnFamilyStore.java:1200 - Flushed to
> [BigTableReader(path='/mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db\
> ')] (1 sstables, 4.838KiB), biggest 4.838KiB, smallest 4.838KiB
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@12f3d291[id=45fcb286-b87a-3d18-a04b-b899a9880c91,name=test_c_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=c}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:121 - to rebuild: index:
> BigTableReader(path='/mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big-Data.db'),
> sstable: org.apache.cassa\
> ndra.index.sasi.conf.ColumnIndex@6cbb6b0e
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:129 - Rebuilding SASI
> Indexes:
> {BigTableRead
[jira] [Commented] (CASSANDRA-12962) SASI: Index are rebuilt on restart
[
https://issues.apache.org/jira/browse/CASSANDRA-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935163#comment-15935163
]
Alex Petrov commented on CASSANDRA-12962:
-
[~jjirsa] thanks for the hint. I have indeed missed that little insert with two
columns that do not include {{c}} (and ran tests that didn't account for this
edge case). I think in this case we have to build a placeholder index or
something similar that'd make sure we don't rebuild it.
[~iksaif] should I take it or did you plan to work on it?
> SASI: Index are rebuilt on restart
> --
>
> Key: CASSANDRA-12962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12962
> Project: Cassandra
> Issue Type: Improvement
> Components: sasi
>Reporter: Corentin Chary
>Priority: Minor
> Fix For: 3.11.x
>
>
> Apparently when cassandra any index that does not index a value in *every*
> live SSTable gets rebuild. The offending code can be found in the constructor
> of SASIIndex.
> You can easilly reproduce it:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE test.test (
> a text PRIMARY KEY,
> b text,
> c text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX test_b_idx ON test.test (b) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> CREATE CUSTOM INDEX test_c_idx ON test.test (c) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> INSERT INTO test.test (a, b) VALUES ('a', 'b');
> {code}
> Log (I added additional traces):
> {code}
> INFO [main] 2016-11-28 15:32:21,191 ColumnFamilyStore.java:406 -
> Initializing test.test
> DEBUG [SSTableBatchOpen:1] 2016-11-28 15:32:21,192 SSTableReader.java:505 -
> Opening
> /mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big
> (0.034KiB)
> DEBUG [main] 2016-11-28 15:32:21,194 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@2f661b1a[id=6b00489b-7010-396e-9348-9f32f5167f88,name=test_b_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=b}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> INFO [main] 2016-11-28 15:32:21,194 DataTracker.java:152 -
> SSTableIndex.open(column: b, minTerm: value, maxTerm: value, minKey: key,
> maxKey: key, sstable: BigTableReader(path='/mnt/ssd/tmp/data/data/test/test\
> -229e6380b57711e68407158fde22e121/mc-1-big-Data.db'))
> DEBUG [main] 2016-11-28 15:32:21,195 SASIIndex.java:129 - Rebuilding SASI
> Indexes: {}
> DEBUG [main] 2016-11-28 15:32:21,195 ColumnFamilyStore.java:895 - Enqueuing
> flush of IndexInfo: 0.386KiB (0%) on-heap, 0.000KiB (0%) off-heap
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:465 - Writing Memtable-IndexInfo@748981977(0.054KiB serialized
> bytes, 1 ops, 0%/0% of on/off-heap limit), flushed range = (min(-9223\
> 372036854775808), max(9223372036854775807)]
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:494 - Completed flushing
> /mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db
> (0.035KiB) for\
> commitlog position CommitLogPosition(segmentId=1480343535479, position=15652)
> DEBUG [MemtableFlushWriter:1] 2016-11-28 15:32:21,224
> ColumnFamilyStore.java:1200 - Flushed to
> [BigTableReader(path='/mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db\
> ')] (1 sstables, 4.838KiB), biggest 4.838KiB, smallest 4.838KiB
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@12f3d291[id=45fcb286-b87a-3d18-a04b-b899a9880c91,name=test_c_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=c}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:121 - to rebuild: index:
> BigTableReader(path='/mnt/ssd/tmp/data/d
[jira] [Commented] (CASSANDRA-12962) SASI: Index are rebuilt on restart
[
https://issues.apache.org/jira/browse/CASSANDRA-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935166#comment-15935166
]
Corentin Chary commented on CASSANDRA-12962:
Exact. In my degenerate case I had 64 columns, all indexed but most data was
sparse. This lead to ~2h rebuilds after each restarts.
> SASI: Index are rebuilt on restart
> --
>
> Key: CASSANDRA-12962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12962
> Project: Cassandra
> Issue Type: Improvement
> Components: sasi
>Reporter: Corentin Chary
>Priority: Minor
> Fix For: 3.11.x
>
>
> Apparently when cassandra any index that does not index a value in *every*
> live SSTable gets rebuild. The offending code can be found in the constructor
> of SASIIndex.
> You can easilly reproduce it:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE test.test (
> a text PRIMARY KEY,
> b text,
> c text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX test_b_idx ON test.test (b) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> CREATE CUSTOM INDEX test_c_idx ON test.test (c) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> INSERT INTO test.test (a, b) VALUES ('a', 'b');
> {code}
> Log (I added additional traces):
> {code}
> INFO [main] 2016-11-28 15:32:21,191 ColumnFamilyStore.java:406 -
> Initializing test.test
> DEBUG [SSTableBatchOpen:1] 2016-11-28 15:32:21,192 SSTableReader.java:505 -
> Opening
> /mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big
> (0.034KiB)
> DEBUG [main] 2016-11-28 15:32:21,194 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@2f661b1a[id=6b00489b-7010-396e-9348-9f32f5167f88,name=test_b_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=b}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> INFO [main] 2016-11-28 15:32:21,194 DataTracker.java:152 -
> SSTableIndex.open(column: b, minTerm: value, maxTerm: value, minKey: key,
> maxKey: key, sstable: BigTableReader(path='/mnt/ssd/tmp/data/data/test/test\
> -229e6380b57711e68407158fde22e121/mc-1-big-Data.db'))
> DEBUG [main] 2016-11-28 15:32:21,195 SASIIndex.java:129 - Rebuilding SASI
> Indexes: {}
> DEBUG [main] 2016-11-28 15:32:21,195 ColumnFamilyStore.java:895 - Enqueuing
> flush of IndexInfo: 0.386KiB (0%) on-heap, 0.000KiB (0%) off-heap
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:465 - Writing Memtable-IndexInfo@748981977(0.054KiB serialized
> bytes, 1 ops, 0%/0% of on/off-heap limit), flushed range = (min(-9223\
> 372036854775808), max(9223372036854775807)]
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:494 - Completed flushing
> /mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db
> (0.035KiB) for\
> commitlog position CommitLogPosition(segmentId=1480343535479, position=15652)
> DEBUG [MemtableFlushWriter:1] 2016-11-28 15:32:21,224
> ColumnFamilyStore.java:1200 - Flushed to
> [BigTableReader(path='/mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db\
> ')] (1 sstables, 4.838KiB), biggest 4.838KiB, smallest 4.838KiB
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@12f3d291[id=45fcb286-b87a-3d18-a04b-b899a9880c91,name=test_c_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=c}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:121 - to rebuild: index:
> BigTableReader(path='/mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big-Data.db'),
> sstable: org.apache.cassa\
> ndra.index.sasi.conf.ColumnIndex@6cbb6b0e
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:129 - Rebuildin
[jira] [Commented] (CASSANDRA-12962) SASI: Index are rebuilt on restart
[
https://issues.apache.org/jira/browse/CASSANDRA-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935157#comment-15935157
]
Jeff Jirsa commented on CASSANDRA-12962:
I think, if I'm reading it properly, [~iksaif] asserts that {{c}} doesn't need
an index build, because {{c}} has no data. If you were to restart again, {{c}}
would be rebuilt again, because it will continue to have no data, because the
INSERT was limited {{INSERT INTO test.test (a, b) VALUES ('a', 'b');}} .
Presumably in a large enough data set, this rebuild is reasonably expensive and
perhaps there's a way to avoid it?
> SASI: Index are rebuilt on restart
> --
>
> Key: CASSANDRA-12962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12962
> Project: Cassandra
> Issue Type: Improvement
> Components: sasi
>Reporter: Corentin Chary
>Priority: Minor
> Fix For: 3.11.x
>
>
> Apparently when cassandra any index that does not index a value in *every*
> live SSTable gets rebuild. The offending code can be found in the constructor
> of SASIIndex.
> You can easilly reproduce it:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '1'} AND durable_writes = true;
> CREATE TABLE test.test (
> a text PRIMARY KEY,
> b text,
> c text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> CREATE CUSTOM INDEX test_b_idx ON test.test (b) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> CREATE CUSTOM INDEX test_c_idx ON test.test (c) USING
> 'org.apache.cassandra.index.sasi.SASIIndex';
> INSERT INTO test.test (a, b) VALUES ('a', 'b');
> {code}
> Log (I added additional traces):
> {code}
> INFO [main] 2016-11-28 15:32:21,191 ColumnFamilyStore.java:406 -
> Initializing test.test
> DEBUG [SSTableBatchOpen:1] 2016-11-28 15:32:21,192 SSTableReader.java:505 -
> Opening
> /mnt/ssd/tmp/data/data/test/test-229e6380b57711e68407158fde22e121/mc-1-big
> (0.034KiB)
> DEBUG [main] 2016-11-28 15:32:21,194 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@2f661b1a[id=6b00489b-7010-396e-9348-9f32f5167f88,name=test_b_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=b}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> INFO [main] 2016-11-28 15:32:21,194 DataTracker.java:152 -
> SSTableIndex.open(column: b, minTerm: value, maxTerm: value, minKey: key,
> maxKey: key, sstable: BigTableReader(path='/mnt/ssd/tmp/data/data/test/test\
> -229e6380b57711e68407158fde22e121/mc-1-big-Data.db'))
> DEBUG [main] 2016-11-28 15:32:21,195 SASIIndex.java:129 - Rebuilding SASI
> Indexes: {}
> DEBUG [main] 2016-11-28 15:32:21,195 ColumnFamilyStore.java:895 - Enqueuing
> flush of IndexInfo: 0.386KiB (0%) on-heap, 0.000KiB (0%) off-heap
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:465 - Writing Memtable-IndexInfo@748981977(0.054KiB serialized
> bytes, 1 ops, 0%/0% of on/off-heap limit), flushed range = (min(-9223\
> 372036854775808), max(9223372036854775807)]
> DEBUG [PerDiskMemtableFlushWriter_0:1] 2016-11-28 15:32:21,204
> Memtable.java:494 - Completed flushing
> /mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db
> (0.035KiB) for\
> commitlog position CommitLogPosition(segmentId=1480343535479, position=15652)
> DEBUG [MemtableFlushWriter:1] 2016-11-28 15:32:21,224
> ColumnFamilyStore.java:1200 - Flushed to
> [BigTableReader(path='/mnt/ssd/tmp/data/data/system/IndexInfo-9f5c6374d48532299a0a5094af9ad1e3/mc-4256-big-Data.db\
> ')] (1 sstables, 4.838KiB), biggest 4.838KiB, smallest 4.838KiB
> DEBUG [main] 2016-11-28 15:32:21,224 SASIIndex.java:118 - index:
> org.apache.cassandra.schema.IndexMetadata@12f3d291[id=45fcb286-b87a-3d18-a04b-b899a9880c91,name=test_c_idx,kind=CUSTOM,options={class_name=org.a\
> pache.cassandra.index.sasi.SASIIndex, target=c}], base CFS(Keyspace='test',
> ColumnFamily='test'), tracker
> org.apache.cassandra.db.lifecycle.Tracker@15900b83
> DEBUG [main] 2016-11-28 15:32:21,224 SA
[jira] [Assigned] (CASSANDRA-13358) AlterViewStatement.checkAccess can throw exceptions
[
https://issues.apache.org/jira/browse/CASSANDRA-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Jirsa reassigned CASSANDRA-13358:
--
Assignee: Hao Zhong
> AlterViewStatement.checkAccess can throw exceptions
> ---
>
> Key: CASSANDRA-13358
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13358
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
>Reporter: Hao Zhong
>Assignee: Hao Zhong
>
> The AlterViewStatement.checkAccess method has code lines as follow:
> {code:title=AlterViewStatement.java|borderStyle=solid}
> if (baseTable != null)
> state.hasColumnFamilyAccess(keyspace(), baseTable.name,
> Permission.ALTER);
> {code}
> These lines can throw InvalidRequestException. Indeed,
> DropTableStatement.checkAccess has a similar problem, and was fixed in
> CASSANDRA-6687. The fixed code is as follow:
> {code:title=DropTableStatement.java|borderStyle=solid}
> try
> {
> state.hasColumnFamilyAccess(keyspace(), columnFamily(),
> Permission.DROP);
> }
> catch (InvalidRequestException e)
> {
> if (!ifExists)
> throw e;
> }
> {code}
> Please fix the problem as CASSANDRA-6687 did.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13333) Cassandra does not start on Windows due to 'JNA link failure'
[
https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-1:
---
Status: Patch Available (was: Open)
> Cassandra does not start on Windows due to 'JNA link failure'
> -
>
> Key: CASSANDRA-1
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1
> Project: Cassandra
> Issue Type: Bug
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Blocker
>
> Cassandra 3.0 HEAD does not start on Windows. The only error in the logs is:
> {{ERROR 16:30:10 JNA failing to initialize properly.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13333) Cassandra does not start on Windows due to 'JNA link failure'
[
https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934880#comment-15934880
]
Benjamin Lerer commented on CASSANDRA-1:
||[3.0|https://github.com/apache/cassandra/compare/trunk...blerer:1-3.0]|[utests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-1-3.0-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-1-3.0-dtest/]|
||[3.11|https://github.com/apache/cassandra/compare/trunk...blerer:1-3.11]|[utests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-1-3.11-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-1-3.11-dtest/]|
||[trunk|https://github.com/apache/cassandra/compare/trunk...blerer:trunk]|[utests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-1-trunk-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-1-trunk-dtest/]|
[~jasobrown], [~mkjellman] could one of you review the patches. Only 3.0 and
3.11 differ a bit.
> Cassandra does not start on Windows due to 'JNA link failure'
> -
>
> Key: CASSANDRA-1
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1
> Project: Cassandra
> Issue Type: Bug
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>Priority: Blocker
>
> Cassandra 3.0 HEAD does not start on Windows. The only error in the logs is:
> {{ERROR 16:30:10 JNA failing to initialize properly.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CASSANDRA-11935) Add support for arithmetic operators
[
https://issues.apache.org/jira/browse/CASSANDRA-11935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer resolved CASSANDRA-11935.
Resolution: Fixed
> Add support for arithmetic operators
>
>
> Key: CASSANDRA-11935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11935
> Project: Cassandra
> Issue Type: Sub-task
> Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
> Fix For: 4.0
>
>
> The goal of this ticket is to add support for arithmetic operators:
> * {{-}}: Change the sign of the argument
> * {{+}}: Addition operator
> * {{-}}: Minus operator
> * {{*}}: Multiplication operator
> * {{/}}: Division operator
> * {{%}}: Modulo operator
> This ticket we should focus on adding operator only for numeric types to keep
> the scope as small as possible. Dates and string operations will be adressed
> in follow up tickets.
> The operation precedence should be:
> # {{*}}, {{/}}, {{%}}
> # {{+}}, {{-}}
> Some implicit data conversion should be performed when operations are
> performed on different types (e.g. double + int).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-11935) Add support for arithmetic operators
[
https://issues.apache.org/jira/browse/CASSANDRA-11935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934848#comment-15934848
]
Benjamin Lerer commented on CASSANDRA-11935:
Committed into trunk at f5e0a7cdba7c361c04ac21f49f6e5e20af502b9e
> Add support for arithmetic operators
>
>
> Key: CASSANDRA-11935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11935
> Project: Cassandra
> Issue Type: Sub-task
> Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
> Fix For: 4.0
>
>
> The goal of this ticket is to add support for arithmetic operators:
> * {{-}}: Change the sign of the argument
> * {{+}}: Addition operator
> * {{-}}: Minus operator
> * {{*}}: Multiplication operator
> * {{/}}: Division operator
> * {{%}}: Modulo operator
> This ticket we should focus on adding operator only for numeric types to keep
> the scope as small as possible. Dates and string operations will be adressed
> in follow up tickets.
> The operation precedence should be:
> # {{*}}, {{/}}, {{%}}
> # {{+}}, {{-}}
> Some implicit data conversion should be performed when operations are
> performed on different types (e.g. double + int).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
cassandra git commit: Fix SmallInt and TinyInt serialization (Followup CASSANDRA-11935)
Repository: cassandra
Updated Branches:
refs/heads/trunk 3177de5d7 -> f5e0a7cdb
Fix SmallInt and TinyInt serialization (Followup CASSANDRA-11935)
patch by Benjamin Lerer; reviewed by Sylvain Lebresne for CASSANDRA-11935
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f5e0a7cd
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f5e0a7cd
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f5e0a7cd
Branch: refs/heads/trunk
Commit: f5e0a7cdba7c361c04ac21f49f6e5e20af502b9e
Parents: 3177de5
Author: Benjamin Lerer
Authored: Tue Mar 21 17:08:18 2017 +0100
Committer: Benjamin Lerer
Committed: Tue Mar 21 17:08:18 2017 +0100
--
.../org/apache/cassandra/cql3/functions/OperationFcts.java | 8
src/java/org/apache/cassandra/db/marshal/ByteType.java | 6 --
src/java/org/apache/cassandra/db/marshal/ShortType.java | 6 --
3 files changed, 8 insertions(+), 12 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/f5e0a7cd/src/java/org/apache/cassandra/cql3/functions/OperationFcts.java
--
diff --git a/src/java/org/apache/cassandra/cql3/functions/OperationFcts.java
b/src/java/org/apache/cassandra/cql3/functions/OperationFcts.java
index 9232fc1..4994660 100644
--- a/src/java/org/apache/cassandra/cql3/functions/OperationFcts.java
+++ b/src/java/org/apache/cassandra/cql3/functions/OperationFcts.java
@@ -297,6 +297,14 @@ public final class OperationFcts
if (size > 0)
return size;
+// tinyint and smallint type are not fixed length types even if they
should be.
+// So we need to handle them in a special way.
+if (type == ByteType.instance)
+return 1;
+
+if (type == ShortType.instance)
+return 2;
+
if (type.isCounter())
return LongType.instance.valueLengthIfFixed();
http://git-wip-us.apache.org/repos/asf/cassandra/blob/f5e0a7cd/src/java/org/apache/cassandra/db/marshal/ByteType.java
--
diff --git a/src/java/org/apache/cassandra/db/marshal/ByteType.java
b/src/java/org/apache/cassandra/db/marshal/ByteType.java
index 517e734..c19fdd9 100644
--- a/src/java/org/apache/cassandra/db/marshal/ByteType.java
+++ b/src/java/org/apache/cassandra/db/marshal/ByteType.java
@@ -84,12 +84,6 @@ public class ByteType extends NumberType
}
@Override
-public int valueLengthIfFixed()
-{
-return 1;
-}
-
-@Override
public TypeSerializer getSerializer()
{
return ByteSerializer.instance;
http://git-wip-us.apache.org/repos/asf/cassandra/blob/f5e0a7cd/src/java/org/apache/cassandra/db/marshal/ShortType.java
--
diff --git a/src/java/org/apache/cassandra/db/marshal/ShortType.java
b/src/java/org/apache/cassandra/db/marshal/ShortType.java
index b37a0b7..01dca4e 100644
--- a/src/java/org/apache/cassandra/db/marshal/ShortType.java
+++ b/src/java/org/apache/cassandra/db/marshal/ShortType.java
@@ -93,12 +93,6 @@ public class ShortType extends NumberType
}
@Override
-public int valueLengthIfFixed()
-{
-return 2;
-}
-
-@Override
public short toShort(ByteBuffer value)
{
return ByteBufferUtil.toShort(value);
[jira] [Assigned] (CASSANDRA-13275) Cassandra throws an exception during CQL select query filtering on map key
[
https://issues.apache.org/jira/browse/CASSANDRA-13275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer reassigned CASSANDRA-13275:
--
Assignee: Alex Petrov (was: Benjamin Lerer)
> Cassandra throws an exception during CQL select query filtering on map key
> ---
>
> Key: CASSANDRA-13275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13275
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
>Reporter: Abderrahmane CHRAIBI
>Assignee: Alex Petrov
>
> Env: cqlsh 5.0.1 | Cassandra 3.9 | CQL spec 3.4.2 | Native protocol v4
> Using this table structure:
> {code}CREATE TABLE mytable (
> mymap frozen>>> PRIMARY KEY
> )
> {code}
> Executing:
> {code} select * from mytable where mymap contains key UUID;
> {code}
> Within cqlsh shows this message:
> {code}
> ServerError: java.lang.UnsupportedOperationException
> system.log:
> java.lang.UnsupportedOperationException: null
> at
> org.apache.cassandra.cql3.restrictions.SingleColumnRestriction$ContainsRestriction.appendTo(SingleColumnRestriction.java:456)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.restrictions.PartitionKeySingleRestrictionSet.values(PartitionKeySingleRestrictionSet.java:86)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.restrictions.StatementRestrictions.getPartitionKeys(StatementRestrictions.java:585)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.getSliceCommands(SelectStatement.java:474)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.getQuery(SelectStatement.java:262)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:227)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:76)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:188)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:219)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:204)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:115)
> ~[apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:513)
> [apache-cassandra-3.9.jar:3.9]
> at
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:407)
> [apache-cassandra-3.9.jar:3.9]
> at
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> [netty-all-4.0.39.Final.jar:4.0.39.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
> [netty-all-4.0.39.Final.jar:4.0.39.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:35)
> [netty-all-4.0.39.Final.jar:4.0.39.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:357)
> [netty-all-4.0.39.Final.jar:4.0.39.Final]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
> [apache-cassandra-3.9.jar:3.9]
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109)
> [apache-cassandra-3.9.jar:3.9]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-11935) Add support for arithmetic operators
[
https://issues.apache.org/jira/browse/CASSANDRA-11935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934792#comment-15934792
]
Sylvain Lebresne commented on CASSANDRA-11935:
--
lgtm, +1.
> Add support for arithmetic operators
>
>
> Key: CASSANDRA-11935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11935
> Project: Cassandra
> Issue Type: Sub-task
> Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
> Fix For: 4.0
>
>
> The goal of this ticket is to add support for arithmetic operators:
> * {{-}}: Change the sign of the argument
> * {{+}}: Addition operator
> * {{-}}: Minus operator
> * {{*}}: Multiplication operator
> * {{/}}: Division operator
> * {{%}}: Modulo operator
> This ticket we should focus on adding operator only for numeric types to keep
> the scope as small as possible. Dates and string operations will be adressed
> in follow up tickets.
> The operation precedence should be:
> # {{*}}, {{/}}, {{%}}
> # {{+}}, {{-}}
> Some implicit data conversion should be performed when operations are
> performed on different types (e.g. double + int).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13284) break CQL specification & reference parser into separate repo
[ https://issues.apache.org/jira/browse/CASSANDRA-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934778#comment-15934778 ] Jon Haddad commented on CASSANDRA-13284: [~ifesdjeen] Yes, you're right. I put this in here as a placeholder with the intent to bring it up on the ML, but I forgot to send it. > break CQL specification & reference parser into separate repo > - > > Key: CASSANDRA-13284 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13284 > Project: Cassandra > Issue Type: Improvement >Reporter: Jon Haddad > > It would be pretty awesome to be able to use the CQL parser in other > projects, such as a driver, developer studio, etc. I propose we break out > the CQL spec and parser into a sub-project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-11935) Add support for arithmetic operators
[
https://issues.apache.org/jira/browse/CASSANDRA-11935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934775#comment-15934775
]
Benjamin Lerer commented on CASSANDRA-11935:
I pushed a patch to fix the problem.
||[trunk|https://github.com/apache/cassandra/compare/trunk...blerer:11935-2-trunk]|[utests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11935-2-trunk-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11935-2-trunk-dtest/lastCompletedBuild/testReport/]|
> Add support for arithmetic operators
>
>
> Key: CASSANDRA-11935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11935
> Project: Cassandra
> Issue Type: Sub-task
> Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
> Fix For: 4.0
>
>
> The goal of this ticket is to add support for arithmetic operators:
> * {{-}}: Change the sign of the argument
> * {{+}}: Addition operator
> * {{-}}: Minus operator
> * {{*}}: Multiplication operator
> * {{/}}: Division operator
> * {{%}}: Modulo operator
> This ticket we should focus on adding operator only for numeric types to keep
> the scope as small as possible. Dates and string operations will be adressed
> in follow up tickets.
> The operation precedence should be:
> # {{*}}, {{/}}, {{%}}
> # {{+}}, {{-}}
> Some implicit data conversion should be performed when operations are
> performed on different types (e.g. double + int).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CASSANDRA-12238) Unexpected exception during request java.lang.IndexOutOfBoundsException: null
[
https://issues.apache.org/jira/browse/CASSANDRA-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov resolved CASSANDRA-12238.
-
Resolution: Cannot Reproduce
> Unexpected exception during request java.lang.IndexOutOfBoundsException: null
> -
>
> Key: CASSANDRA-12238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12238
> Project: Cassandra
> Issue Type: Bug
> Environment: datastax-ddc-3.7.0, CentOS 7, x86, JDK 1.8.0u91
>Reporter: Gábor Auth
>
> Our two DCs and eight nodes cluster throws sometimes:
> {code}
> ERROR [SharedPool-Worker-25] 2016-07-19 16:22:14,643 ErrorMessage.java:338 -
> Unexpected exception during request
> java.lang.IndexOutOfBoundsException: null
> at java.nio.Buffer.checkIndex(Buffer.java:546) ~[na:1.8.0_91]
> at java.nio.HeapByteBuffer.getShort(HeapByteBuffer.java:314)
> ~[na:1.8.0_91]
> at
> org.apache.cassandra.db.context.CounterContext.headerLength(CounterContext.java:141)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.access$100(CounterContext.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.(CounterContext.java:758)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.wrap(CounterContext.java:765)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.merge(CounterContext.java:271)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.Conflicts.mergeCounterValues(Conflicts.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Cells.reconcile(Cells.java:143)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:614)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:572)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Row$Merger.merge(Row.java:549)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:473)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:437)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:419)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:279)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:112)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.FilteredRows.isEmpty(FilteredRows.java:30)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.closeIfEmpty(Filter.java:49)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:22)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:6)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:735)
> ~[apache-cassandra-
[jira] [Commented] (CASSANDRA-12238) Unexpected exception during request java.lang.IndexOutOfBoundsException: null
[
https://issues.apache.org/jira/browse/CASSANDRA-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934750#comment-15934750
]
Alex Petrov commented on CASSANDRA-12238:
-
Right, sorry, I didn't notice the timestamp. I'll close with can't reproduce
for now.
> Unexpected exception during request java.lang.IndexOutOfBoundsException: null
> -
>
> Key: CASSANDRA-12238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12238
> Project: Cassandra
> Issue Type: Bug
> Environment: datastax-ddc-3.7.0, CentOS 7, x86, JDK 1.8.0u91
>Reporter: Gábor Auth
>
> Our two DCs and eight nodes cluster throws sometimes:
> {code}
> ERROR [SharedPool-Worker-25] 2016-07-19 16:22:14,643 ErrorMessage.java:338 -
> Unexpected exception during request
> java.lang.IndexOutOfBoundsException: null
> at java.nio.Buffer.checkIndex(Buffer.java:546) ~[na:1.8.0_91]
> at java.nio.HeapByteBuffer.getShort(HeapByteBuffer.java:314)
> ~[na:1.8.0_91]
> at
> org.apache.cassandra.db.context.CounterContext.headerLength(CounterContext.java:141)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.access$100(CounterContext.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.(CounterContext.java:758)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.wrap(CounterContext.java:765)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.merge(CounterContext.java:271)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.Conflicts.mergeCounterValues(Conflicts.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Cells.reconcile(Cells.java:143)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:614)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:572)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Row$Merger.merge(Row.java:549)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:473)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:437)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:419)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:279)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:112)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.FilteredRows.isEmpty(FilteredRows.java:30)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.closeIfEmpty(Filter.java:49)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:22)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:6)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
>
[jira] [Commented] (CASSANDRA-12238) Unexpected exception during request java.lang.IndexOutOfBoundsException: null
[
https://issues.apache.org/jira/browse/CASSANDRA-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934746#comment-15934746
]
Gábor Auth commented on CASSANDRA-12238:
Hm... unfortunately, I don't know, it was almost a year ago... :/
> Unexpected exception during request java.lang.IndexOutOfBoundsException: null
> -
>
> Key: CASSANDRA-12238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12238
> Project: Cassandra
> Issue Type: Bug
> Environment: datastax-ddc-3.7.0, CentOS 7, x86, JDK 1.8.0u91
>Reporter: Gábor Auth
>
> Our two DCs and eight nodes cluster throws sometimes:
> {code}
> ERROR [SharedPool-Worker-25] 2016-07-19 16:22:14,643 ErrorMessage.java:338 -
> Unexpected exception during request
> java.lang.IndexOutOfBoundsException: null
> at java.nio.Buffer.checkIndex(Buffer.java:546) ~[na:1.8.0_91]
> at java.nio.HeapByteBuffer.getShort(HeapByteBuffer.java:314)
> ~[na:1.8.0_91]
> at
> org.apache.cassandra.db.context.CounterContext.headerLength(CounterContext.java:141)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.access$100(CounterContext.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.(CounterContext.java:758)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.wrap(CounterContext.java:765)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.merge(CounterContext.java:271)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.Conflicts.mergeCounterValues(Conflicts.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Cells.reconcile(Cells.java:143)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:614)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:572)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Row$Merger.merge(Row.java:549)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:473)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:437)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:419)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:279)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:112)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.FilteredRows.isEmpty(FilteredRows.java:30)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.closeIfEmpty(Filter.java:49)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:22)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:6)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.c
[jira] [Assigned] (CASSANDRA-13169) testall failure in org.apache.cassandra.index.sasi.disk.OnDiskIndexTest.testSparseMode-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-13169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov reassigned CASSANDRA-13169:
---
Assignee: Alex Petrov
> testall failure in
> org.apache.cassandra.index.sasi.disk.OnDiskIndexTest.testSparseMode-compression
> --
>
> Key: CASSANDRA-13169
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13169
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
>Reporter: Sean McCarthy
>Assignee: Alex Petrov
> Labels: test-failure, testall
> Attachments:
> TEST-org.apache.cassandra.index.sasi.disk.OnDiskIndexTest.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_testall/1376/testReport/org.apache.cassandra.index.sasi.disk/OnDiskIndexTest/testSparseMode_compression
> {code}
> Error Message
> expected:<-1> but was:<0>
> {code}{code}
> Stacktrace
> junit.framework.AssertionFailedError: expected:<-1> but was:<0>
> at
> org.apache.cassandra.index.sasi.disk.OnDiskIndexTest.testSparseMode(OnDiskIndexTest.java:350)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CASSANDRA-13176) DROP INDEX seemingly doesn't stop existing Index build
[ https://issues.apache.org/jira/browse/CASSANDRA-13176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov reassigned CASSANDRA-13176: --- Assignee: Alex Petrov > DROP INDEX seemingly doesn't stop existing Index build > -- > > Key: CASSANDRA-13176 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13176 > Project: Cassandra > Issue Type: Bug > Components: Compaction, CQL > Environment: CentOS Linux, JRE 1.8 >Reporter: Soumya Sanyal >Assignee: Alex Petrov > > There appears to be an edge case with secondary indexes (non SASI). I > originally issued a CREATE INDEX on a column, and upon listening to advice > from folks in the #cassandra room, decided against it, and issued a DROP > INDEX. > I didn't check the cluster overnight, but this morning, I found out that our > cluster CPU usage was pegged around 80%. Looking at compaction stats, I saw > that the index build was still ongoing. We had to restart the entire cluster > for the changes to take effect. > Version: 3.9 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CASSANDRA-13243) testall failure in org.apache.cassandra.index.sasi.SASIIndexTest.testMultiExpressionQueriesWhereRowSplitBetweenSSTables-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-13243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov reassigned CASSANDRA-13243:
---
Assignee: Alex Petrov
> testall failure in
> org.apache.cassandra.index.sasi.SASIIndexTest.testMultiExpressionQueriesWhereRowSplitBetweenSSTables-compression
> ---
>
> Key: CASSANDRA-13243
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13243
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
>Reporter: Sean McCarthy
>Assignee: Alex Petrov
> Labels: test-failure, testall
> Attachments: TEST-org.apache.cassandra.index.sasi.SASIIndexTest.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_testall/1412/testReport/org.apache.cassandra.index.sasi/SASIIndexTest/testMultiExpressionQueriesWhereRowSplitBetweenSSTables_compression
> {code}
> Error Message
> [key0, key11, key12, key13, key14, key6, key7, key8] expected:<10> but was:<8>
> {code}{code}
> Stacktrace
> junit.framework.AssertionFailedError: [key0, key11, key12, key13, key14,
> key6, key7, key8] expected:<10> but was:<8>
> at
> org.apache.cassandra.index.sasi.SASIIndexTest.testMultiExpressionQueriesWhereRowSplitBetweenSSTables(SASIIndexTest.java:567)
> at
> org.apache.cassandra.index.sasi.SASIIndexTest.testMultiExpressionQueriesWhereRowSplitBetweenSSTables(SASIIndexTest.java:452)
> {code}{code}
> Standard Output
> ERROR [main] 2017-02-17 23:02:40,404 ?:? - SLF4J: stderr
> INFO [main] 2017-02-17 23:02:40,830 ?:? - Configuration location:
> file:/home/automaton/cassandra/test/conf/cassandra-murmur.yaml
> DEBUG [main] 2017-02-17 23:02:40,831 ?:? - Loading settings from
> file:/home/automaton/cassandra/test/conf/cassandra-murmur.yaml
> INFO [main] 2017-02-17 23:02:41,678 ?:? - Node
> configuration:[allocate_tokens_for_keyspace=null; authenticator=null;
> authorizer=null; auto_bootstrap=true; auto_snapshot=true; back_pres
> ...[truncated 416882 chars]...
> .957KiB), biggest 4.957KiB, smallest 4.957KiB
> DEBUG [CompactionExecutor:3] 2017-02-17 23:03:16,787 ?:? - Compacted
> (cb40-f565-11e6-8e91-7511b7f59d65) 4 sstables to
> [/home/automaton/cassandra/build/test/cassandra/data:231/system/local-7ad54392bcdd35a684174e047860b377/md-85-big,]
> to level=0. 0.466KiB to 0.258KiB (~55% of original) in 58ms. Read
> Throughput = 7.914KiB/s, Write Throughput = 4.380KiB/s, Row Throughput =
> ~2/s. 4 total partitions merged to 1. Partition merge counts were {4:1, }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13284) break CQL specification & reference parser into separate repo
[ https://issues.apache.org/jira/browse/CASSANDRA-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934731#comment-15934731 ] Alex Petrov commented on CASSANDRA-13284: - I might have missed it entirely, but wouldn't it be better to just trigger a discussion on the mailing list? > break CQL specification & reference parser into separate repo > - > > Key: CASSANDRA-13284 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13284 > Project: Cassandra > Issue Type: Improvement >Reporter: Jon Haddad > > It would be pretty awesome to be able to use the CQL parser in other > projects, such as a driver, developer studio, etc. I propose we break out > the CQL spec and parser into a sub-project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13322) testall failure in org.apache.cassandra.io.compress.CompressedRandomAccessReaderTest.testDataCorruptionDetection-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934727#comment-15934727
]
Alex Petrov commented on CASSANDRA-13322:
-
Unfortunately, since this is a randomised test, we may possibly end up with
non-corrupted data. We can do retries, but then we'll only decrease
probability, it still may happen that we will write data that won't corrupt the
sstable every once in a while.
What we should do, however, is making a {{Random}} there based on a seed and
print seed in test results, to make it reproducible.
> testall failure in
> org.apache.cassandra.io.compress.CompressedRandomAccessReaderTest.testDataCorruptionDetection-compression
>
>
> Key: CASSANDRA-13322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13322
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
>Reporter: Sean McCarthy
> Labels: test-failure, testall
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_testall/658/testReport/org.apache.cassandra.io.compress/CompressedRandomAccessReaderTest/testDataCorruptionDetection_compression
> {code}
> Stacktrace
> junit.framework.AssertionFailedError:
> at
> org.apache.cassandra.io.compress.CompressedRandomAccessReaderTest.testDataCorruptionDetection(CompressedRandomAccessReaderTest.java:218)
> {code}{code}
> Standard Output
> WARN 10:58:45 open(null, O_RDONLY) failed, errno (14).
> WARN 10:58:45 open(null, O_RDONLY) failed, errno (14).
> WARN 10:58:45 open(null, O_RDONLY) failed, errno (14).
> WARN 10:58:45 open(null, O_RDONLY) failed, errno (14).
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13359) Cleanup ParentRepairSession after repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-13359: Resolution: Fixed Status: Resolved (was: Ready to Commit) > Cleanup ParentRepairSession after repairs > - > > Key: CASSANDRA-13359 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13359 > Project: Cassandra > Issue Type: Bug >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Minor > Fix For: 4.0 > > > As part of removing anti-compaction code in CASSANDRA-9143, the call the > removeParentRepairSession was not moved into the repair complete callback. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CASSANDRA-13334) Cassandra fails to start with LOCAL_JMX set to false
[
https://issues.apache.org/jira/browse/CASSANDRA-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934725#comment-15934725
]
Alex Petrov commented on CASSANDRA-13334:
-
Cassandra requires proper security if you enable non-local JMX connection,
you'll have to provide a {{jmxremote.passwd}}. You can find more information
for example
[here|https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/secureJmxAuthentication.html]
(I just picked the first google search result that was relevant, there're
other guides online as well).
> Cassandra fails to start with LOCAL_JMX set to false
>
>
> Key: CASSANDRA-13334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13334
> Project: Cassandra
> Issue Type: Bug
> Components: Lifecycle
> Environment: cassandra 3.0.9
> ubuntu 16.04
> ec2
>Reporter: Andres March
> Fix For: 3.0.x
>
>
> There seems to be some changes lately with CASSANDRA-11540 and
> CASSANDRA-11725 that changes how remote jmx set up works.
> Just setting LOCAL_JMX=false causes cassandra to fail to start on ubuntu in
> ec2. Worse yet the initd script says it has started ok and there are no logs
> whatsoever about an error.
> This is reproducible 100% of the time. Changing various settings like the
> port, jmx remote hostname, etc... didn't change anything. I would attach
> some logs but there aren't any.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
cassandra git commit: ninja: updating CHANGES.txt
Repository: cassandra Updated Branches: refs/heads/trunk e9cc5878a -> 3177de5d7 ninja: updating CHANGES.txt Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3177de5d Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3177de5d Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3177de5d Branch: refs/heads/trunk Commit: 3177de5d79aeb583e9118e258714669b9cec66f5 Parents: e9cc587 Author: Blake Eggleston Authored: Tue Mar 21 07:41:04 2017 -0700 Committer: Blake Eggleston Committed: Tue Mar 21 07:41:04 2017 -0700 -- CHANGES.txt | 1 + 1 file changed, 1 insertion(+) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3177de5d/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 70d4a3f..2d3c521 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.0 + * Cleanup ParentRepairSession after repairs (CASSANDRA-13359) * Incremental repair not streaming correct sstables (CASSANDRA-13328) * Upgrade the jna version to 4.3.0 (CASSANDRA-13300) * Add the currentTimestamp, currentDate, currentTime and currentTimeUUID functions (CASSANDRA-13132)
cassandra git commit: Cleanup ParentRepairSession after repairs
Repository: cassandra
Updated Branches:
refs/heads/trunk 5b8b1ce26 -> e9cc5878a
Cleanup ParentRepairSession after repairs
Patch by Blake Eggleston; reviewed by Marcus Eriksson for CASSANDRA-13359
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e9cc5878
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/e9cc5878
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/e9cc5878
Branch: refs/heads/trunk
Commit: e9cc5878a1cfea77bbf8316c9e5b0013d1aa9b82
Parents: 5b8b1ce
Author: Blake Eggleston
Authored: Tue Mar 21 07:29:12 2017 -0700
Committer: Blake Eggleston
Committed: Tue Mar 21 07:37:09 2017 -0700
--
src/java/org/apache/cassandra/repair/RepairRunnable.java | 1 +
1 file changed, 1 insertion(+)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/e9cc5878/src/java/org/apache/cassandra/repair/RepairRunnable.java
--
diff --git a/src/java/org/apache/cassandra/repair/RepairRunnable.java
b/src/java/org/apache/cassandra/repair/RepairRunnable.java
index 422dbdb..7d9c1d6 100644
--- a/src/java/org/apache/cassandra/repair/RepairRunnable.java
+++ b/src/java/org/apache/cassandra/repair/RepairRunnable.java
@@ -440,6 +440,7 @@ public class RepairRunnable extends WrappedRunnable
implements ProgressEventNoti
private void repairComplete()
{
+
ActiveRepairService.instance.removeParentRepairSession(parentSession);
String duration =
DurationFormatUtils.formatDurationWords(System.currentTimeMillis() - startTime,
true,
true);
String message = String.format("Repair command #%d finished in
%s", cmd, duration);
[jira] [Commented] (CASSANDRA-12238) Unexpected exception during request java.lang.IndexOutOfBoundsException: null
[
https://issues.apache.org/jira/browse/CASSANDRA-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934720#comment-15934720
]
Alex Petrov commented on CASSANDRA-12238:
-
It would be great to know under which conditions this is triggered: what the
schema is, what query exactly this was.
> Unexpected exception during request java.lang.IndexOutOfBoundsException: null
> -
>
> Key: CASSANDRA-12238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12238
> Project: Cassandra
> Issue Type: Bug
> Environment: datastax-ddc-3.7.0, CentOS 7, x86, JDK 1.8.0u91
>Reporter: Gábor Auth
>
> Our two DCs and eight nodes cluster throws sometimes:
> {code}
> ERROR [SharedPool-Worker-25] 2016-07-19 16:22:14,643 ErrorMessage.java:338 -
> Unexpected exception during request
> java.lang.IndexOutOfBoundsException: null
> at java.nio.Buffer.checkIndex(Buffer.java:546) ~[na:1.8.0_91]
> at java.nio.HeapByteBuffer.getShort(HeapByteBuffer.java:314)
> ~[na:1.8.0_91]
> at
> org.apache.cassandra.db.context.CounterContext.headerLength(CounterContext.java:141)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.access$100(CounterContext.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.(CounterContext.java:758)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext$ContextState.wrap(CounterContext.java:765)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.context.CounterContext.merge(CounterContext.java:271)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.Conflicts.mergeCounterValues(Conflicts.java:76)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Cells.reconcile(Cells.java:143)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:614)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:572)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.rows.Row$Merger.merge(Row.java:549)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:473)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:437)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:419)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:279)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:112)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.FilteredRows.isEmpty(FilteredRows.java:30)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.closeIfEmpty(Filter.java:49)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:22)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:6)
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76)
> ~[apache-cassandra-3
[jira] [Commented] (CASSANDRA-13359) Cleanup ParentRepairSession after repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934716#comment-15934716 ] Marcus Eriksson commented on CASSANDRA-13359: - +1 > Cleanup ParentRepairSession after repairs > - > > Key: CASSANDRA-13359 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13359 > Project: Cassandra > Issue Type: Bug >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Minor > Fix For: 4.0 > > > As part of removing anti-compaction code in CASSANDRA-9143, the call the > removeParentRepairSession was not moved into the repair complete callback. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CASSANDRA-12674) [SASI] Confusing AND/OR semantics for StandardAnalyzer
[
https://issues.apache.org/jira/browse/CASSANDRA-12674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov reassigned CASSANDRA-12674:
---
Assignee: Alex Petrov
> [SASI] Confusing AND/OR semantics for StandardAnalyzer
> ---
>
> Key: CASSANDRA-12674
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12674
> Project: Cassandra
> Issue Type: Bug
> Components: sasi
> Environment: Cassandra 3.7
>Reporter: DOAN DuyHai
>Assignee: Alex Petrov
>
> {code:sql}
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.7 | CQL spec 3.4.2 | Native protocol v4]
> Use HELP for help.
> cqlsh> use test;
> cqlsh:test> CREATE TABLE sasi_bug(id int, clustering int, val text, PRIMARY
> KEY((id), clustering));
> cqlsh:test> CREATE CUSTOM INDEX ON sasi_bug(val) USING
> 'org.apache.cassandra.index.sasi.SASIIndex' WITH OPTIONS = {
> 'mode': 'CONTAINS',
> 'analyzer_class':
> 'org.apache.cassandra.index.sasi.analyzer.StandardAnalyzer',
> 'analyzed': 'true'};
> //1st example SAME PARTITION KEY
> cqlsh:test> INSERT INTO sasi_bug(id, clustering , val ) VALUES(1, 1,
> 'homeworker');
> cqlsh:test> INSERT INTO sasi_bug(id, clustering , val ) VALUES(1, 2,
> 'hardworker');
> cqlsh:test> SELECT * FROM sasi_bug WHERE val LIKE '%work home%';
> id | clustering | val
> ++
> 1 | 1 | homeworker
> 1 | 2 | hardworker
> (2 rows)
> //2nd example DIFFERENT PARTITION KEY
> cqlsh:test> INSERT INTO sasi_bug(id, clustering, val) VALUES(10, 1,
> 'speedrun');
> cqlsh:test> INSERT INTO sasi_bug(id, clustering, val) VALUES(11, 1,
> 'longrun');
> cqlsh:test> SELECT * FROM sasi_bug WHERE val LIKE '%long run%';
> id | clustering | val
> ++-
> 11 | 1 | longrun
> (1 rows)
> {code}
> In the 1st example, both rows belong to the same partition so SASI returns
> both values. Indeed {{LIKE '%work home%'}} means {{contains 'work' OR
> 'home'}} so the result makes sense
> In the 2nd example, only one row is returned whereas we expect 2 rows because
> {{LIKE '%long run%'}} means {{contains 'long' OR 'run'}} so *speedrun* should
> be returned too.
> So where is the problem ? Explanation:
> When there is only 1 predicate, the root operation type is an *AND*:
> {code:java|title=QueryPlan}
> private Operation analyze()
> {
> try
> {
> Operation.Builder and = new Operation.Builder(OperationType.AND,
> controller);
> controller.getExpressions().forEach(and::add);
> return and.complete();
> }
>...
> }
> {code}
> During the parsing of {{LIKE '%long run%'}}, SASI creates 2 expressions for
> the searched term: {{long}} and {{run}}, which corresponds to an *OR* logic.
> However, this piece of code just ruins the *OR* logic:
> {code:java|title=Operation}
> public Operation complete()
> {
> if (!expressions.isEmpty())
> {
> ListMultimap
> analyzedExpressions = analyzeGroup(controller, op, expressions);
> RangeIterator.Builder range =
> controller.getIndexes(op, analyzedExpressions.values());
> ...
> }
> {code}
> As you can see, we blindly take all the *values* of the MultiMap (which
> contains a single entry for the {{val}} column with 2 expressions) and pass
> it to {{controller.getIndexes(...)}}
> {code:java|title=QueryController}
> public RangeIterator.Builder getIndexes(OperationType op,
> Collection expressions)
> {
> if (resources.containsKey(expressions))
> throw new IllegalArgumentException("Can't process the same
> expressions multiple times.");
> RangeIterator.Builder builder = op == OperationType.OR
> ? RangeUnionIterator. Token>builder()
> :
> RangeIntersectionIterator.builder();
> ...
> }
> {code}
> And because the root operation has *AND* type, the
> {{RangeIntersectionIterator}} will be used on both expressions {{long}} and
> {{run}}.
> So when data belong to different partitions, we have the *AND* logic that
> applies and eliminates _speedrun_
> When data belong to the same partition but different row, the
> {{RangeIntersectionIterator}} returns a single partition and then the rows
> are filtered further by {{operationTree.satisfiedBy}} and the results are
> correct
> {code:java|title=QueryPlan}
> while (currentKeys.hasNext())
> {
> DecoratedKey key = currentKeys.next();
> if (!keyRange.right.isMinimum() &&
> keyRange.right.compareTo(key) < 0)
> return endOfData();
> try (UnfilteredRowIterator partition =
[jira] [Updated] (CASSANDRA-13359) Cleanup ParentRepairSession after repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-13359: Status: Ready to Commit (was: Patch Available) > Cleanup ParentRepairSession after repairs > - > > Key: CASSANDRA-13359 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13359 > Project: Cassandra > Issue Type: Bug >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Minor > Fix For: 4.0 > > > As part of removing anti-compaction code in CASSANDRA-9143, the call the > removeParentRepairSession was not moved into the repair complete callback. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13359) Cleanup ParentRepairSession after repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-13359: Status: Patch Available (was: Open) patch here: https://github.com/bdeggleston/cassandra/commits/13359 > Cleanup ParentRepairSession after repairs > - > > Key: CASSANDRA-13359 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13359 > Project: Cassandra > Issue Type: Bug >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Minor > Fix For: 4.0 > > > As part of removing anti-compaction code in CASSANDRA-9143, the call the > removeParentRepairSession was not moved into the repair complete callback. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
