[cassandra-website] branch asf-staging updated (1abf36c8 -> f8d78d73)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 1abf36c8 generate docs for 8efdf127 new f8d78d73 generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1abf36c8) \ N -- N -- N refs/heads/asf-staging (f8d78d73) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (0e7746ee -> 1abf36c8)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 0e7746ee generate docs for 8efdf127 new 1abf36c8 generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0e7746ee) \ N -- N -- N refs/heads/asf-staging (1abf36c8) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (9a0b30964 -> 0e7746ee1)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 9a0b30964 generate docs for 8efdf127 new 0e7746ee1 generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (9a0b30964) \ N -- N -- N refs/heads/asf-staging (0e7746ee1) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18534) Make sstable format configurable per table
[
https://issues.apache.org/jira/browse/CASSANDRA-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733316#comment-17733316
]
Maxwell Guo commented on CASSANDRA-18534:
-
Hello, as for this ticket ,I am going to make these SSTable format settings
both in cassandra.yam and table level in TableParams (So I think there will be
a new ticket for cassandra's driver~~~ ).
The strength of the validity of the configuration is table level > yaml . if
both yaml and table param is setted. Table level validity is greater，then yaml
's .If none of them is setted, use the default.
Organization of table-level parameters can be a map , like compaction.
Besides, I think we have to modify the cqlsh and add dtest as I have done for
CASSANDRA-15402.
> Make sstable format configurable per table
> --
>
> Key: CASSANDRA-18534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18534
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Branimir Lambov
>Assignee: Maxwell Guo
>Priority: Normal
>
> Some SSTable format settings need to be configurable per table for better
> efficiency. This includes:
> - {{row_index_granularity}}
> - {{bloom_filter_fp_chance}}
> - {{crc_check_chance}}
> - {{min/max_index_interval}}
> Some of these are currently configurable using direct properties of tables.
> Having them as format properties makes better sense and should also support
> specifying useable combinations of settings, e.g.
> {code:java}
> CREATE TABLE ... WITH sstable_format = "bti-fast";
> CREATE TABLE ... WITH sstable_format = "bti-small";
> {code}
> where {{bti-fast}} and {{bti-small}} can be defined in {{cassandra.yaml}}
> e.g. as
> {code:java}
> sstable.format.options:
> - bti-fast:
> row_index_granularity: 1kiB
> bloom_filter_fp_chance: 0.01
> - bti-small:
> row_index_granularity: 32kiB
> bloom_filter_fp_chance: 0.1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18605) Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes
[ https://issues.apache.org/jira/browse/CASSANDRA-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733312#comment-17733312 ] Jyothsna Konisa commented on CASSANDRA-18605: - Circle CI link https://app.circleci.com/pipelines/github/jyothsnakonisa/cassandra-analytics/6/workflows/fb4372a1-53c5-4a55-aeb7-3eea556cbe2d > Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes > - > > Key: CASSANDRA-18605 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18605 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > In this patch we are adding support for Spark Bulk Writer writes with TTL & > Timestamp. TTL/ Timestamp can be constant where all rows in the RDD are > written with same TTL/Timestamp or per row based where each row has a > corresponding TTL/Timestamp present in a separate column in the RDD. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17992) Upgrade Netty on 5.0
[ https://issues.apache.org/jira/browse/CASSANDRA-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733261#comment-17733261 ] Ekaterina Dimitrova commented on CASSANDRA-17992: - bq. I have not been able to replicate this outside of circle, with any Java version. At least we have the logs in CircleCI, and we can add additional logging and spin it in the multiplexer. I hope it will still pop up as flaky, at least in the CircleCI multiplexer? > Upgrade Netty on 5.0 > > > Key: CASSANDRA-17992 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17992 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > Fix For: 5.x > > > I haven't been able to identify from the Netty docs which was the lowest > version where JDK17 was added but we are about 40 versions behind in netty 4 > so I suspect we better update. > -We need to consider there was an issue with class cast exceptions when > building with JDK17 with newer versions of netty (the newest available in > March 2022). For the record, we didn't see those when running CI on JDK8 and > JDK11. We also need to carefully revise the changes between the netty > versions. -->- CASSANDRA-18180 > Upgrading will cover also a fix in netty that was discussed in > [this|https://the-asf.slack.com/archives/CK23JSY2K/p1665567660202989] ASF > Slack thread. > CC [~benedict] , [~aleksey] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18180) bulkLoaderSuccessfullyStreamsOverSsl fails with ClassCastException on JDK17
[
https://issues.apache.org/jira/browse/CASSANDRA-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-18180:
Reviewers: Andres de la Peña, Ekaterina Dimitrova (was: Ekaterina
Dimitrova)
> bulkLoaderSuccessfullyStreamsOverSsl fails with ClassCastException on JDK17
> ---
>
> Key: CASSANDRA-18180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18180
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: dan jatnieks
>Priority: Normal
> Fix For: 5.x
>
> Attachments: cassandra-18180-directbufferref.diff
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While working on CASSANDRA-17992 we hit:
> {code:java}
> java.lang.ClassCastException: class
> org.apache.cassandra.utils.memory.BufferPool$Chunk cannot be cast to class
> sun.nio.ch.DirectBuffer (org.apache.cassandra.utils.memory.BufferPool$Chunk
> is in unnamed module of loader 'app'; sun.nio.ch.DirectBuffer is in module
> java.base of loader 'bootstrap')\n\tat
> java.base/com.sun.crypto.provider.GaloisCounterMode$GCMEngine.overlapDetection(GaloisCounterMode.java:865)\n\tat
>
> java.base/com.sun.crypto.provider.GaloisCounterMode$GCMDecrypt.doFinal(GaloisCounterMode.java:1502)\n\tat
>
> java.base/com.sun.crypto.provider.GaloisCounterMode.engineDoFinal(GaloisCounterMode.java:447)\n\tat
>
> {code}
> -The issue is exposed with JDK 17, trunk; if interested, ping- [~e.dimitrova]
> -for current branch as there is no feature branch at the moment- we can
> build and start from trunk with JDK17 already. Circle CI can be run for JDK17
> too. For more information how to do that - .circleci/readme.md
> CC [~benedict]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18180) bulkLoaderSuccessfullyStreamsOverSsl fails with ClassCastException on JDK17
[
https://issues.apache.org/jira/browse/CASSANDRA-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733252#comment-17733252
]
Ekaterina Dimitrova commented on CASSANDRA-18180:
-
I am still looking into this, but I wanted to ask [~djatnieks] to open a PR
with the latest branch where we can add comments and keep things in one place.
Thank you in advance. I also mentioned some addition needed for Intellij to
work with the new exports
[here|https://github.com/djatnieks/cassandra/commit/9b2e993e11dc5905843fa1f4c52ea5f5437b301e#r118268304]
> bulkLoaderSuccessfullyStreamsOverSsl fails with ClassCastException on JDK17
> ---
>
> Key: CASSANDRA-18180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18180
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: dan jatnieks
>Priority: Normal
> Fix For: 5.x
>
> Attachments: cassandra-18180-directbufferref.diff
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While working on CASSANDRA-17992 we hit:
> {code:java}
> java.lang.ClassCastException: class
> org.apache.cassandra.utils.memory.BufferPool$Chunk cannot be cast to class
> sun.nio.ch.DirectBuffer (org.apache.cassandra.utils.memory.BufferPool$Chunk
> is in unnamed module of loader 'app'; sun.nio.ch.DirectBuffer is in module
> java.base of loader 'bootstrap')\n\tat
> java.base/com.sun.crypto.provider.GaloisCounterMode$GCMEngine.overlapDetection(GaloisCounterMode.java:865)\n\tat
>
> java.base/com.sun.crypto.provider.GaloisCounterMode$GCMDecrypt.doFinal(GaloisCounterMode.java:1502)\n\tat
>
> java.base/com.sun.crypto.provider.GaloisCounterMode.engineDoFinal(GaloisCounterMode.java:447)\n\tat
>
> {code}
> -The issue is exposed with JDK 17, trunk; if interested, ping- [~e.dimitrova]
> -for current branch as there is no feature branch at the moment- we can
> build and start from trunk with JDK17 already. Circle CI can be run for JDK17
> too. For more information how to do that - .circleci/readme.md
> CC [~benedict]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18606) Fix cross-refs in trunk - incorrect syntax, no components
[
https://issues.apache.org/jira/browse/CASSANDRA-18606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorina Poland updated CASSANDRA-18606:
--
Change Category: Operability
Complexity: Low Hanging Fruit
Status: Open (was: Triage Needed)
Only trunk needs fixing.
> Fix cross-refs in trunk - incorrect syntax, no components
> -
>
> Key: CASSANDRA-18606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18606
> Project: Cassandra
> Issue Type: Task
> Components: Documentation
>Reporter: Lorina Poland
>Assignee: Lorina Poland
>Priority: Normal
>
> The nav.adoc in modules/cassandra has xrefs with:
> {code:java}
> xref:developing:data-modeling/filename.adoc
> {code}
> when they should be:
> {code:java}
> xref:developing/data-modeling/filename.adoc
> {code}
> Issue arose due to the flattened antora component structure of the Apache C*
> docs (only ROOT and cassandra).
> All xrefs need fixing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18606) Fix cross-refs in trunk - incorrect syntax, no components
Lorina Poland created CASSANDRA-18606:
-
Summary: Fix cross-refs in trunk - incorrect syntax, no components
Key: CASSANDRA-18606
URL: https://issues.apache.org/jira/browse/CASSANDRA-18606
Project: Cassandra
Issue Type: Task
Components: Documentation
Reporter: Lorina Poland
Assignee: Lorina Poland
The nav.adoc in modules/cassandra has xrefs with:
{code:java}
xref:developing:data-modeling/filename.adoc
{code}
when they should be:
{code:java}
xref:developing/data-modeling/filename.adoc
{code}
Issue arose due to the flattened antora component structure of the Apache C*
docs (only ROOT and cassandra).
All xrefs need fixing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18605) Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes
[ https://issues.apache.org/jira/browse/CASSANDRA-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyothsna Konisa updated CASSANDRA-18605: Test and Documentation Plan: Added test cases and ran `SampleCassandraJob` to verify that writes with TTL & Timestamp are working Status: Patch Available (was: Open) https://github.com/apache/cassandra-analytics/pull/7 > Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes > - > > Key: CASSANDRA-18605 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18605 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > In this patch we are adding support for Spark Bulk Writer writes with TTL & > Timestamp. TTL/ Timestamp can be constant where all rows in the RDD are > written with same TTL/Timestamp or per row based where each row has a > corresponding TTL/Timestamp present in a separate column in the RDD. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18605) Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes
[ https://issues.apache.org/jira/browse/CASSANDRA-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyothsna Konisa updated CASSANDRA-18605: Change Category: Performance Complexity: Normal Component/s: Analytics Library Mentor: Francisco Guerrero Reviewers: Dinesh Joshi, Francisco Guerrero Assignee: Jyothsna Konisa Status: Open (was: Triage Needed) > Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes > - > > Key: CASSANDRA-18605 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18605 > Project: Cassandra > Issue Type: New Feature > Components: Analytics Library >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > In this patch we are adding support for Spark Bulk Writer writes with TTL & > Timestamp. TTL/ Timestamp can be constant where all rows in the RDD are > written with same TTL/Timestamp or per row based where each row has a > corresponding TTL/Timestamp present in a separate column in the RDD. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[GitHub] [cassandra-analytics] jyothsnakonisa opened a new pull request, #7: CASSANDRA-18605 Adding support for TTL & Timestamps for bulk writes
jyothsnakonisa opened a new pull request, #7: URL: https://github.com/apache/cassandra-analytics/pull/7 This commit introduces a new feature in Spark Bulk Writer to support writes with constant/per_row based TTL & Timestamps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18588) Slow builds due to checkstyle
[ https://issues.apache.org/jira/browse/CASSANDRA-18588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733224#comment-17733224 ] Brandon Williams commented on CASSANDRA-18588: -- bq. Unfortunately, going backwards in branches almost always requires it I think git worktrees solves this by keeping each branch in its own directory. > Slow builds due to checkstyle > - > > Key: CASSANDRA-18588 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18588 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1.3, 5.0 > > > Builds are terribly slow atm due to checkstyle. But there's an option to > cache results and only run on the latest changed files to avoid running over > the same files over and over again. > This brings build times from the current 1m30s to the old 5s. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17992) Upgrade Netty on 5.0
[ https://issues.apache.org/jira/browse/CASSANDRA-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733219#comment-17733219 ] Brandon Williams commented on CASSANDRA-17992: -- bq. I'll see if I can figure out what's going on with the ttl_test failure. I have not been able to replicate this outside of circle, with any java version. > Upgrade Netty on 5.0 > > > Key: CASSANDRA-17992 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17992 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > Fix For: 5.x > > > I haven't been able to identify from the Netty docs which was the lowest > version where JDK17 was added but we are about 40 versions behind in netty 4 > so I suspect we better update. > -We need to consider there was an issue with class cast exceptions when > building with JDK17 with newer versions of netty (the newest available in > March 2022). For the record, we didn't see those when running CI on JDK8 and > JDK11. We also need to carefully revise the changes between the netty > versions. -->- CASSANDRA-18180 > Upgrading will cover also a fix in netty that was discussed in > [this|https://the-asf.slack.com/archives/CK23JSY2K/p1665567660202989] ASF > Slack thread. > CC [~benedict] , [~aleksey] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18605) Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes
[ https://issues.apache.org/jira/browse/CASSANDRA-18605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyothsna Konisa updated CASSANDRA-18605: Summary: Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes (was: Cassandra Analytics - Adding support for TTL & Timestamps during bulk writes) > Cassandra Analytics - Adding support for TTL & Timestamps for bulk writes > - > > Key: CASSANDRA-18605 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18605 > Project: Cassandra > Issue Type: New Feature >Reporter: Jyothsna Konisa >Priority: Normal > > In this patch we are adding support for Spark Bulk Writer writes with TTL & > Timestamp. TTL/ Timestamp can be constant where all rows in the RDD are > written with same TTL/Timestamp or per row based where each row has a > corresponding TTL/Timestamp present in a separate column in the RDD. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18605) Cassandra Analytics - Adding support for TTL & Timestamps during bulk writes
Jyothsna Konisa created CASSANDRA-18605: --- Summary: Cassandra Analytics - Adding support for TTL & Timestamps during bulk writes Key: CASSANDRA-18605 URL: https://issues.apache.org/jira/browse/CASSANDRA-18605 Project: Cassandra Issue Type: New Feature Reporter: Jyothsna Konisa In this patch we are adding support for Spark Bulk Writer writes with TTL & Timestamp. TTL/ Timestamp can be constant where all rows in the RDD are written with same TTL/Timestamp or per row based where each row has a corresponding TTL/Timestamp present in a separate column in the RDD. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18604) Write docs for CEP-30 Vector Search
[ https://issues.apache.org/jira/browse/CASSANDRA-18604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18604: --- Summary: Write docs for CEP-30 Vector Search (was: Write docs for CEP-30) > Write docs for CEP-30 Vector Search > --- > > Key: CASSANDRA-18604 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18604 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > > Write docs for Vector search. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18604) Write docs for CEP-30
[ https://issues.apache.org/jira/browse/CASSANDRA-18604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorina Poland updated CASSANDRA-18604: -- Change Category: Operability Complexity: Challenging Status: Open (was: Triage Needed) > Write docs for CEP-30 > - > > Key: CASSANDRA-18604 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18604 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > > Write docs for Vector search. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18604) Write docs for CEP-30
Lorina Poland created CASSANDRA-18604: - Summary: Write docs for CEP-30 Key: CASSANDRA-18604 URL: https://issues.apache.org/jira/browse/CASSANDRA-18604 Project: Cassandra Issue Type: Task Components: Documentation Reporter: Lorina Poland Assignee: Lorina Poland Write docs for Vector search. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (6e3aaa5ea -> 9a0b30964)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 6e3aaa5ea generate docs for 8efdf127 new 9a0b30964 generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (6e3aaa5ea) \ N -- N -- N refs/heads/asf-staging (9a0b30964) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18504) Added support for type VECTOR
[ https://issues.apache.org/jira/browse/CASSANDRA-18504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733177#comment-17733177 ] David Capwell commented on CASSANDRA-18504: --- spoke with [~adelapena] and we are going to block vectors from being reachable from UDFs for now, and once client work is ready we can look to add; that way no breaking changes happen... We may also want to relook at this layer, as its very easy for new types to not know about this... I only got lucky that someone asked how they add to this class without breaking things (good timing)... Either have AbstractType return a DataType, or rethink things... this layer "mimics" client, but actually isn't client (different package)... > Added support for type VECTOR > -- > > Key: CASSANDRA-18504 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18504 > Project: Cassandra > Issue Type: Improvement > Components: Cluster/Schema, CQL/Syntax >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > Time Spent: 19.5h > Remaining Estimate: 0h > > Based off several mailing list threads (see "[POLL] Vector type for ML”, > "[DISCUSS] New data type for vector search”, and "Adding vector search to SAI > with heirarchical navigable small world graph index”), its desirable to add a > new type “VECTOR” that has the following properties > 1) fixed length array > 2) elements may not be null > 3) flatten array (aka multi-cell = false) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18563) Convert AccordStateCache cache from write-through to write-back
[
https://issues.apache.org/jira/browse/CASSANDRA-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733169#comment-17733169
]
Aleksey Yeschenko commented on CASSANDRA-18563:
---
Accord PR with a change to {{IntrusiveLinkedList}}:
https://github.com/apache/cassandra-accord/pull/51
> Convert AccordStateCache cache from write-through to write-back
> ---
>
> Key: CASSANDRA-18563
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18563
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 5.0
>
>
> Pre-requisite work for soon to go up PRs that continue shifting the bulk of
> persistence from system tables to {{AccordJournal}}. The switch to write-back
> caching should allow to bypass writes to the system tables entirely for some
> of the transactions.
> Additionally fixes some bugs in the cache, e.g. {{AsyncLoader}} failing to
> load an object could cause entries to be forever stuck in {{PENDING}} state
> because it would never reach the code path that submits the load runnables to
> the executor (that is now the job of the cache). Also switched the list
> implementation from a hand-rolled ad-hoc one to the pre-existing
> {{IntrusiveLinkedList}}, plus various simplifications and cleanup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18596) Assertion error when describing mv as table
[
https://issues.apache.org/jira/browse/CASSANDRA-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18596:
-
Status: Needs Committer (was: Patch Available)
> Assertion error when describing mv as table
> ---
>
> Key: CASSANDRA-18596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18596
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Maciej Sokol
>Assignee: Maciej Sokol
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When describing materialized view as a table Cassandra gets an assertion
> error.
> Steps to reproduce:
> CREATE KEYSPACE test WITH replication = \{'class': 'NetworkTopologyStrategy',
> 'datacenter1': '3'} AND durable_writes = true;
> CREATE TABLE test.table1 (key1 text,key2 int,value int,PRIMARY KEY (key1,
> key2));
> CREATE MATERIALIZED VIEW test.table1_by_value AS SELECT key1, key2, value
> FROM test.table1 WHERE value IS NOT NULL AND key1 IS NOT NULL AND key2 IS NOT
> NULL PRIMARY KEY(value, key1, key2);
> DESCRIBE MATERIALIZED VIEW test.table1;
> DESCRIBE TABLE test.table1_by_value;
> DESCRIBE TABLE test.non_existing;
>
> From the above the "DESCRIBE TABLE test.table1_by_value;" throws an assertion
> error while "DESCRIBE TABLE test.non_existing;" returns a meaningful error
> msg.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18596) Assertion error when describing mv as table
[
https://issues.apache.org/jira/browse/CASSANDRA-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733168#comment-17733168
]
Brandon Williams commented on CASSANDRA-18596:
--
4.0: CASSANDRA-18366, the infamous CASSANDRA-16677
4.1: unrelated auth_test timeout
trunk: CASSANDRA-18440
+1 from me.
> Assertion error when describing mv as table
> ---
>
> Key: CASSANDRA-18596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18596
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Maciej Sokol
>Assignee: Maciej Sokol
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When describing materialized view as a table Cassandra gets an assertion
> error.
> Steps to reproduce:
> CREATE KEYSPACE test WITH replication = \{'class': 'NetworkTopologyStrategy',
> 'datacenter1': '3'} AND durable_writes = true;
> CREATE TABLE test.table1 (key1 text,key2 int,value int,PRIMARY KEY (key1,
> key2));
> CREATE MATERIALIZED VIEW test.table1_by_value AS SELECT key1, key2, value
> FROM test.table1 WHERE value IS NOT NULL AND key1 IS NOT NULL AND key2 IS NOT
> NULL PRIMARY KEY(value, key1, key2);
> DESCRIBE MATERIALIZED VIEW test.table1;
> DESCRIBE TABLE test.table1_by_value;
> DESCRIBE TABLE test.non_existing;
>
> From the above the "DESCRIBE TABLE test.table1_by_value;" throws an assertion
> error while "DESCRIBE TABLE test.non_existing;" returns a meaningful error
> msg.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18592) CIDR filtering authorizer for Cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-18592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shailaja Koppu updated CASSANDRA-18592: --- Change Category: Operability Status: Open (was: Triage Needed) > CIDR filtering authorizer for Cassandra > --- > > Key: CASSANDRA-18592 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18592 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Authorization >Reporter: Shailaja Koppu >Assignee: Shailaja Koppu >Priority: Normal > Labels: authorization, cidr, features, security > Time Spent: 0.5h > Remaining Estimate: 0h > > Introducing a new authorizer, to allow or disallow users accesses based on > client's IP or CIDR group. Please see the confluence page for requirements > and detailed design of this feature > [https://cwiki.apache.org/confluence/display/CASSANDRA/CIDR+filtering+authorizer]. > Will post PR link and dev discussion soon. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (094c6354d -> 6e3aaa5ea)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 094c6354d generate docs for 8efdf127 new 6e3aaa5ea generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (094c6354d) \ N -- N -- N refs/heads/asf-staging (6e3aaa5ea) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18345) Enable streaming SAI components as part of repair
[ https://issues.apache.org/jira/browse/CASSANDRA-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Kolaczkowski updated CASSANDRA-18345: --- Reviewers: Mike Adamson > Enable streaming SAI components as part of repair > - > > Key: CASSANDRA-18345 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18345 > Project: Cassandra > Issue Type: Improvement > Components: Feature/2i Index >Reporter: Mike Adamson >Assignee: Piotr Kolaczkowski >Priority: Normal > Labels: SAI > Fix For: NA > > > SAI registers it's components with the SSTable descriptor expecting them to > form part of the SSTable lifecycle, including streaming. This is not the case. > The current SSTable format in Cassandra uses a fixed set of components > (Components.STREAMING_COMPONENTS) when streaming SSTables. This needs to > change to use the set of components that are registered with a specific > SSTable by calls to SSTable.registerComponents. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18560) Incorrect IP used for gossip across DCs with prefer_local=true
[
https://issues.apache.org/jira/browse/CASSANDRA-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733115#comment-17733115
]
Brandon Williams commented on CASSANDRA-18560:
--
Thanks for the update.
bq. The connection timeout I shared was the only relevant log I could find
Related, I'm having a difficult time coming up with a way to test this.
> Incorrect IP used for gossip across DCs with prefer_local=true
> --
>
> Key: CASSANDRA-18560
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18560
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Brad Vernon
>Assignee: Brandon Williams
>Priority: Urgent
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> After installing a new node using 4.0.10 we experienced a situation where the
> new node attempted to connect to the private ip of a random number of nodes
> remote DCs which are only accessible via public ip for cross dc
> communications.
> The only impact was new nodes outbound connections, inbound from pre-4.0.10
> were not affected. system.peers_v2 (below) showed that the preferred_ip and
> preferred_port as null, only those in 4.0.10 nodes dc have perferred_ip
> values as expected.
> We believe the issue originated with
> https://issues.apache.org/jira/browse/CASSANDRA-16718
> Details on cluster:
> * All nodes have public IP configured as well as private IP
> * Listen/rpc addressrs are configured for private ip, broadcast is public IP
> * prefer_local=true is enabled for all nodes
> The log that showed the connection failing:
> {code:java}
> INFO [Messaging-EventLoop-3-8] 2023-06-01 00:14:21,565 NoSpamLogger.java:92
> -
> /99.81.:7000->/44.208.:7000-URGENT_MESSAGES-[no-channel]
> failed to connectio.netty.channel.ConnectTimeoutException: connection timed
> out: /10.26.5.11:7000 at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576){code}
> 99 and 44 instances can only access each other using public ips.
> gossipinfo output from 4.0.10 node
> {code:java}
> /44.208.
> generation:1661113358
> heartbeat:25267691
> LOAD:25267683:1.7882044268E10
> SCHEMA:24692061:e98b918d-499f-3ccc-8dbe-5af31f685bda
> DC:13:us-east-1
> RACK:15:1a
> RELEASE_VERSION:6:4.0.5
> NET_VERSION:2:12
> HOST_ID:3:9a41e668-060d-4cfe-bb1e-013f5116422d
> RPC_READY:1407:true
> INTERNAL_ADDRESS_AND_PORT:9:10.26.5.11:7000
> NATIVE_ADDRESS_AND_PORT:4:44.208.:9042
> STATUS_WITH_PORT:1393:NORMAL,-2262036356854762881
> SSTABLE_VERSIONS:7:big-nb
> TOKENS:1392: {code}
> Peers output from 4.0.10 node:
> {code:java}
>peer | peer_port | data_center | host_id
> | native_address | native_port | preferred_ip | preferred_port |
> rack | release_version | schema_version |
> tokens+---+-+--++-+--++--+-+--+---
> 44.208. | 7000 | us-east-1 |
> 9a41e668-060d-4cfe-bb1e-013f5116422d | 44.208. |9042 |
> null | null | 1a | 4.0.5 |
> e98b918d-499f-3ccc-8dbe-5af31f685bda |{'-2262036356854762881',
> '-4197710115038136897', '-7072386316096662315', '2085255826742630980',
> '249732489387853170', '4976300208126705818', '7187184456885833289',
> '8777189009399731927'} {code}
> To solve temporarily we routed outbound traffic to the private ip to public
> using iptables which resulted in successful outbound connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18560) Incorrect IP used for gossip across DCs with prefer_local=true
[
https://issues.apache.org/jira/browse/CASSANDRA-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733110#comment-17733110
]
Brad Vernon commented on CASSANDRA-18560:
-
[~brandon.williams] I don't have a debug log when this happened, we only keep
them for a short period of time, but it looks like you were able find the cause
of the problem. The connection timeout I shared was the only relevant log I
could find since the errors were only on the node joining trying to connect to
remote hosts.
I appreciate the quick investigation and attention. If we have another node
that exhibits the same issue I will capture the full logs to share.
> Incorrect IP used for gossip across DCs with prefer_local=true
> --
>
> Key: CASSANDRA-18560
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18560
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Brad Vernon
>Assignee: Brandon Williams
>Priority: Urgent
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> After installing a new node using 4.0.10 we experienced a situation where the
> new node attempted to connect to the private ip of a random number of nodes
> remote DCs which are only accessible via public ip for cross dc
> communications.
> The only impact was new nodes outbound connections, inbound from pre-4.0.10
> were not affected. system.peers_v2 (below) showed that the preferred_ip and
> preferred_port as null, only those in 4.0.10 nodes dc have perferred_ip
> values as expected.
> We believe the issue originated with
> https://issues.apache.org/jira/browse/CASSANDRA-16718
> Details on cluster:
> * All nodes have public IP configured as well as private IP
> * Listen/rpc addressrs are configured for private ip, broadcast is public IP
> * prefer_local=true is enabled for all nodes
> The log that showed the connection failing:
> {code:java}
> INFO [Messaging-EventLoop-3-8] 2023-06-01 00:14:21,565 NoSpamLogger.java:92
> -
> /99.81.:7000->/44.208.:7000-URGENT_MESSAGES-[no-channel]
> failed to connectio.netty.channel.ConnectTimeoutException: connection timed
> out: /10.26.5.11:7000 at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576){code}
> 99 and 44 instances can only access each other using public ips.
> gossipinfo output from 4.0.10 node
> {code:java}
> /44.208.
> generation:1661113358
> heartbeat:25267691
> LOAD:25267683:1.7882044268E10
> SCHEMA:24692061:e98b918d-499f-3ccc-8dbe-5af31f685bda
> DC:13:us-east-1
> RACK:15:1a
> RELEASE_VERSION:6:4.0.5
> NET_VERSION:2:12
> HOST_ID:3:9a41e668-060d-4cfe-bb1e-013f5116422d
> RPC_READY:1407:true
> INTERNAL_ADDRESS_AND_PORT:9:10.26.5.11:7000
> NATIVE_ADDRESS_AND_PORT:4:44.208.:9042
> STATUS_WITH_PORT:1393:NORMAL,-2262036356854762881
> SSTABLE_VERSIONS:7:big-nb
> TOKENS:1392: {code}
> Peers output from 4.0.10 node:
> {code:java}
>peer | peer_port | data_center | host_id
> | native_address | native_port | preferred_ip | preferred_port |
> rack | release_version | schema_version |
> tokens+---+-+--++-+--++--+-+--+---
> 44.208. | 7000 | us-east-1 |
> 9a41e668-060d-4cfe-bb1e-013f5116422d | 44.208. |9042 |
> null | null | 1a | 4.0.5 |
> e98b918d-499f-3ccc-8dbe-5af31f685bda |{'-2262036356854762881',
> '-4197710115038136897', '-7072386316096662315', '2085255826742630980',
> '249732489387853170', '4976300208126705818', '7187184456885833289',
> '8777189009399731927'} {code}
> To solve temporarily we routed outbound traffic to the private ip to public
> using iptables which resulted in successful outbound connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18596) Assertion error when describing mv as table
[
https://issues.apache.org/jira/browse/CASSANDRA-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18596:
-
Reviewers: Brandon Williams
> Assertion error when describing mv as table
> ---
>
> Key: CASSANDRA-18596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18596
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Maciej Sokol
>Assignee: Maciej Sokol
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When describing materialized view as a table Cassandra gets an assertion
> error.
> Steps to reproduce:
> CREATE KEYSPACE test WITH replication = \{'class': 'NetworkTopologyStrategy',
> 'datacenter1': '3'} AND durable_writes = true;
> CREATE TABLE test.table1 (key1 text,key2 int,value int,PRIMARY KEY (key1,
> key2));
> CREATE MATERIALIZED VIEW test.table1_by_value AS SELECT key1, key2, value
> FROM test.table1 WHERE value IS NOT NULL AND key1 IS NOT NULL AND key2 IS NOT
> NULL PRIMARY KEY(value, key1, key2);
> DESCRIBE MATERIALIZED VIEW test.table1;
> DESCRIBE TABLE test.table1_by_value;
> DESCRIBE TABLE test.non_existing;
>
> From the above the "DESCRIBE TABLE test.table1_by_value;" throws an assertion
> error while "DESCRIBE TABLE test.non_existing;" returns a meaningful error
> msg.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18596) Assertion error when describing mv as table
[
https://issues.apache.org/jira/browse/CASSANDRA-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733105#comment-17733105
]
Brandon Williams commented on CASSANDRA-18596:
--
Here we go:
||Branch||CI||
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-18596-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1066/workflows/de2a0254-f430-4dcd-9c55-8db3b374c482],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1066/workflows/48ec8f72-a900-4c10-a973-6c827e1a78be]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-18596-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1068/workflows/7cbdffeb-fcc1-4329-824c-b8bac5b20b18],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1068/workflows/0f549606-b7fa-4220-acf1-79d37799783e]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-18596-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1067/workflows/40fc884f-b93e-4d29-a175-6a19edec2199],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1067/workflows/0509d6cb-78c8-49ae-8554-3ac7a7ace50c]|
> Assertion error when describing mv as table
> ---
>
> Key: CASSANDRA-18596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18596
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Maciej Sokol
>Assignee: Maciej Sokol
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When describing materialized view as a table Cassandra gets an assertion
> error.
> Steps to reproduce:
> CREATE KEYSPACE test WITH replication = \{'class': 'NetworkTopologyStrategy',
> 'datacenter1': '3'} AND durable_writes = true;
> CREATE TABLE test.table1 (key1 text,key2 int,value int,PRIMARY KEY (key1,
> key2));
> CREATE MATERIALIZED VIEW test.table1_by_value AS SELECT key1, key2, value
> FROM test.table1 WHERE value IS NOT NULL AND key1 IS NOT NULL AND key2 IS NOT
> NULL PRIMARY KEY(value, key1, key2);
> DESCRIBE MATERIALIZED VIEW test.table1;
> DESCRIBE TABLE test.table1_by_value;
> DESCRIBE TABLE test.non_existing;
>
> From the above the "DESCRIBE TABLE test.table1_by_value;" throws an assertion
> error while "DESCRIBE TABLE test.non_existing;" returns a meaningful error
> msg.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (b51bcb773 -> 094c6354d)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard b51bcb773 generate docs for 8efdf127 new 094c6354d generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b51bcb773) \ N -- N -- N refs/heads/asf-staging (094c6354d) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14667) Upgrade Dropwizard Metrics to 4.x
[ https://issues.apache.org/jira/browse/CASSANDRA-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733095#comment-17733095 ] Stefan Miklosovic commented on CASSANDRA-14667: --- telepathy! > Upgrade Dropwizard Metrics to 4.x > - > > Key: CASSANDRA-14667 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14667 > Project: Cassandra > Issue Type: Task > Components: Observability/Metrics >Reporter: Stig Rohde Døssing >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Attachments: signature.asc > > Time Spent: 20m > Remaining Estimate: 0h > > Cassandra currently uses Metrics 3.1.5. Version 4.0.0 added some fixes for > Java 9 compatibility. It would be good to upgrade the Metrics library as part > of the version of Cassandra that adds Java 9 compatibility > (https://issues.apache.org/jira/browse/CASSANDRA-9608). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14667) Upgrade Dropwizard Metrics to 4.x
[ https://issues.apache.org/jira/browse/CASSANDRA-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733093#comment-17733093 ] Ekaterina Dimitrova commented on CASSANDRA-14667: - Just one minute ago, I texted [~mmuzaf] in Slack I am going to look into this today or tomorrow :) > Upgrade Dropwizard Metrics to 4.x > - > > Key: CASSANDRA-14667 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14667 > Project: Cassandra > Issue Type: Task > Components: Observability/Metrics >Reporter: Stig Rohde Døssing >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Attachments: signature.asc > > Time Spent: 20m > Remaining Estimate: 0h > > Cassandra currently uses Metrics 3.1.5. Version 4.0.0 added some fixes for > Java 9 compatibility. It would be good to upgrade the Metrics library as part > of the version of Cassandra that adds Java 9 compatibility > (https://issues.apache.org/jira/browse/CASSANDRA-9608). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18595) Dropped table causes node to get stuck in JOINING
[
https://issues.apache.org/jira/browse/CASSANDRA-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733090#comment-17733090
]
Brandon Williams commented on CASSANDRA-18595:
--
Even if this can be fixed it's almost always going to be a bad idea to mix
schema and topology changes simultaneously.
> Dropped table causes node to get stuck in JOINING
> -
>
> Key: CASSANDRA-18595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18595
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Cameron Zemek
>Priority: Normal
> Attachments: cass_stream.patch
>
>
> To facilitate reproducibility of this issue I have created a patch.
> [^cass_stream.patch]
> It can also be reproduced without patch by dropping table while node is doing
> stream for join.
> {code:java}
> cd ~/dev/cassandra
> git checkout 3.11.14
> git apply ~/downloads/cass_stream.patch
> ant clean
> ant
> ccm create -n 3 test
> ccm node1 start
> ccm node2 start
> ccm node1 cqlsh -e "CREATE KEYSPACE test WITH replication = {'class':
> 'NetworkTopologyStrategy', 'datacenter1': '3'};"
> # receive warning since nodes < RF
> ccm node1 cqlsh -e "CREATE TABLE test.streamtest(stream_id int PRIMARY KEY,
> payload TEXT);"
> ccm node1 cqlsh -e "INSERT INTO test.streamtest(stream_id, payload) VALUES(1,
> 'hello world')"
> ccm flush
> sed -i 's/auto_bootstrap: false/auto_bootstrap: true/'
> ~/.ccm/test/node3/node.conf
> sed -i 's/auto_bootstrap: false/auto_bootstrap: true/'
> ~/.ccm/test/node3/conf/cassandra.yaml
> sed -i 's/seeds: 127.0.0.1,127.0.0.2,127.0.0.3/seeds: 127.0.0.1,127.0.0.2/'
> ~/.ccm/test/node3/conf/cassandra.yaml
> touch ~/.ccm/test/node3/logs/system.log
> ccm node3 start
> tail -f ~/.ccm/test/node3/logs/system.log{code}
> The logs will display something like:
> {noformat}
> ERROR [STREAM-IN-/127.0.0.1:7000] 2023-06-14 11:08:37,399
> StreamSession.java:609 - [Stream #fdd71710-0a4f-11ee-a768-c3d20ff8c2d1]
> Streaming error occurred on session with peer 127.0.0.1
> java.io.IOException: streamtest 38f79d70-0a4f-11ee-9849-a999e71c8739 CF was
> dropped during compressed streaming
> ERROR [main] 2023-06-14 11:08:37,405 StorageService.java:1630 - Error while
> waiting on bootstrap to complete. Bootstrap will have to be
> restarted.{noformat}
> The problem is in this use case the customer is rotating out tables every few
> hours and so resuming the bootstrap keeps failing. In my opinion this is a
> bug and Cassandra should be robust enough to continue streaming if a table is
> dropped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18595) Dropped table causes node to get stuck in JOINING
[
https://issues.apache.org/jira/browse/CASSANDRA-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733086#comment-17733086
]
Stefan Miklosovic commented on CASSANDRA-18595:
---
[~samt] any ideas?
> Dropped table causes node to get stuck in JOINING
> -
>
> Key: CASSANDRA-18595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18595
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Cameron Zemek
>Priority: Normal
> Attachments: cass_stream.patch
>
>
> To facilitate reproducibility of this issue I have created a patch.
> [^cass_stream.patch]
> It can also be reproduced without patch by dropping table while node is doing
> stream for join.
> {code:java}
> cd ~/dev/cassandra
> git checkout 3.11.14
> git apply ~/downloads/cass_stream.patch
> ant clean
> ant
> ccm create -n 3 test
> ccm node1 start
> ccm node2 start
> ccm node1 cqlsh -e "CREATE KEYSPACE test WITH replication = {'class':
> 'NetworkTopologyStrategy', 'datacenter1': '3'};"
> # receive warning since nodes < RF
> ccm node1 cqlsh -e "CREATE TABLE test.streamtest(stream_id int PRIMARY KEY,
> payload TEXT);"
> ccm node1 cqlsh -e "INSERT INTO test.streamtest(stream_id, payload) VALUES(1,
> 'hello world')"
> ccm flush
> sed -i 's/auto_bootstrap: false/auto_bootstrap: true/'
> ~/.ccm/test/node3/node.conf
> sed -i 's/auto_bootstrap: false/auto_bootstrap: true/'
> ~/.ccm/test/node3/conf/cassandra.yaml
> sed -i 's/seeds: 127.0.0.1,127.0.0.2,127.0.0.3/seeds: 127.0.0.1,127.0.0.2/'
> ~/.ccm/test/node3/conf/cassandra.yaml
> touch ~/.ccm/test/node3/logs/system.log
> ccm node3 start
> tail -f ~/.ccm/test/node3/logs/system.log{code}
> The logs will display something like:
> {noformat}
> ERROR [STREAM-IN-/127.0.0.1:7000] 2023-06-14 11:08:37,399
> StreamSession.java:609 - [Stream #fdd71710-0a4f-11ee-a768-c3d20ff8c2d1]
> Streaming error occurred on session with peer 127.0.0.1
> java.io.IOException: streamtest 38f79d70-0a4f-11ee-9849-a999e71c8739 CF was
> dropped during compressed streaming
> ERROR [main] 2023-06-14 11:08:37,405 StorageService.java:1630 - Error while
> waiting on bootstrap to complete. Bootstrap will have to be
> restarted.{noformat}
> The problem is in this use case the customer is rotating out tables every few
> hours and so resuming the bootstrap keeps failing. In my opinion this is a
> bug and Cassandra should be robust enough to continue streaming if a table is
> dropped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18560) Incorrect IP used for gossip across DCs with prefer_local=true
[
https://issues.apache.org/jira/browse/CASSANDRA-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733083#comment-17733083
]
Brandon Williams commented on CASSANDRA-18560:
--
Ah, streaming, that makes sense. Perhaps we should have removed the
preferred_ip usage there as well, as I thought about on CASSANDRA-16718 but
decided against... it seems that the compromise was a mistake. I'm not sure we
should take another swing at that for the next release, and perhaps should just
revert CASSANDRA-16718. I'm raising the priority of this ticket to hopefully
block any releases without it while this is in progress.
> Incorrect IP used for gossip across DCs with prefer_local=true
> --
>
> Key: CASSANDRA-18560
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18560
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Brad Vernon
>Assignee: Brandon Williams
>Priority: Urgent
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> After installing a new node using 4.0.10 we experienced a situation where the
> new node attempted to connect to the private ip of a random number of nodes
> remote DCs which are only accessible via public ip for cross dc
> communications.
> The only impact was new nodes outbound connections, inbound from pre-4.0.10
> were not affected. system.peers_v2 (below) showed that the preferred_ip and
> preferred_port as null, only those in 4.0.10 nodes dc have perferred_ip
> values as expected.
> We believe the issue originated with
> https://issues.apache.org/jira/browse/CASSANDRA-16718
> Details on cluster:
> * All nodes have public IP configured as well as private IP
> * Listen/rpc addressrs are configured for private ip, broadcast is public IP
> * prefer_local=true is enabled for all nodes
> The log that showed the connection failing:
> {code:java}
> INFO [Messaging-EventLoop-3-8] 2023-06-01 00:14:21,565 NoSpamLogger.java:92
> -
> /99.81.:7000->/44.208.:7000-URGENT_MESSAGES-[no-channel]
> failed to connectio.netty.channel.ConnectTimeoutException: connection timed
> out: /10.26.5.11:7000 at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576){code}
> 99 and 44 instances can only access each other using public ips.
> gossipinfo output from 4.0.10 node
> {code:java}
> /44.208.
> generation:1661113358
> heartbeat:25267691
> LOAD:25267683:1.7882044268E10
> SCHEMA:24692061:e98b918d-499f-3ccc-8dbe-5af31f685bda
> DC:13:us-east-1
> RACK:15:1a
> RELEASE_VERSION:6:4.0.5
> NET_VERSION:2:12
> HOST_ID:3:9a41e668-060d-4cfe-bb1e-013f5116422d
> RPC_READY:1407:true
> INTERNAL_ADDRESS_AND_PORT:9:10.26.5.11:7000
> NATIVE_ADDRESS_AND_PORT:4:44.208.:9042
> STATUS_WITH_PORT:1393:NORMAL,-2262036356854762881
> SSTABLE_VERSIONS:7:big-nb
> TOKENS:1392: {code}
> Peers output from 4.0.10 node:
> {code:java}
>peer | peer_port | data_center | host_id
> | native_address | native_port | preferred_ip | preferred_port |
> rack | release_version | schema_version |
> tokens+---+-+--++-+--++--+-+--+---
> 44.208. | 7000 | us-east-1 |
> 9a41e668-060d-4cfe-bb1e-013f5116422d | 44.208. |9042 |
> null | null | 1a | 4.0.5 |
> e98b918d-499f-3ccc-8dbe-5af31f685bda |{'-2262036356854762881',
> '-4197710115038136897', '-7072386316096662315', '2085255826742630980',
> '249732489387853170', '4976300208126705818', '7187184456885833289',
> '8777189009399731927'} {code}
> To solve temporarily we routed outbound traffic to the private ip to public
> using iptables which resulted in successful outbound connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18560) Incorrect IP used for gossip across DCs with prefer_local=true
[
https://issues.apache.org/jira/browse/CASSANDRA-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18560:
-
Since Version: 4.0.10
> Incorrect IP used for gossip across DCs with prefer_local=true
> --
>
> Key: CASSANDRA-18560
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18560
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Brad Vernon
>Assignee: Brandon Williams
>Priority: Urgent
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> After installing a new node using 4.0.10 we experienced a situation where the
> new node attempted to connect to the private ip of a random number of nodes
> remote DCs which are only accessible via public ip for cross dc
> communications.
> The only impact was new nodes outbound connections, inbound from pre-4.0.10
> were not affected. system.peers_v2 (below) showed that the preferred_ip and
> preferred_port as null, only those in 4.0.10 nodes dc have perferred_ip
> values as expected.
> We believe the issue originated with
> https://issues.apache.org/jira/browse/CASSANDRA-16718
> Details on cluster:
> * All nodes have public IP configured as well as private IP
> * Listen/rpc addressrs are configured for private ip, broadcast is public IP
> * prefer_local=true is enabled for all nodes
> The log that showed the connection failing:
> {code:java}
> INFO [Messaging-EventLoop-3-8] 2023-06-01 00:14:21,565 NoSpamLogger.java:92
> -
> /99.81.:7000->/44.208.:7000-URGENT_MESSAGES-[no-channel]
> failed to connectio.netty.channel.ConnectTimeoutException: connection timed
> out: /10.26.5.11:7000 at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576){code}
> 99 and 44 instances can only access each other using public ips.
> gossipinfo output from 4.0.10 node
> {code:java}
> /44.208.
> generation:1661113358
> heartbeat:25267691
> LOAD:25267683:1.7882044268E10
> SCHEMA:24692061:e98b918d-499f-3ccc-8dbe-5af31f685bda
> DC:13:us-east-1
> RACK:15:1a
> RELEASE_VERSION:6:4.0.5
> NET_VERSION:2:12
> HOST_ID:3:9a41e668-060d-4cfe-bb1e-013f5116422d
> RPC_READY:1407:true
> INTERNAL_ADDRESS_AND_PORT:9:10.26.5.11:7000
> NATIVE_ADDRESS_AND_PORT:4:44.208.:9042
> STATUS_WITH_PORT:1393:NORMAL,-2262036356854762881
> SSTABLE_VERSIONS:7:big-nb
> TOKENS:1392: {code}
> Peers output from 4.0.10 node:
> {code:java}
>peer | peer_port | data_center | host_id
> | native_address | native_port | preferred_ip | preferred_port |
> rack | release_version | schema_version |
> tokens+---+-+--++-+--++--+-+--+---
> 44.208. | 7000 | us-east-1 |
> 9a41e668-060d-4cfe-bb1e-013f5116422d | 44.208. |9042 |
> null | null | 1a | 4.0.5 |
> e98b918d-499f-3ccc-8dbe-5af31f685bda |{'-2262036356854762881',
> '-4197710115038136897', '-7072386316096662315', '2085255826742630980',
> '249732489387853170', '4976300208126705818', '7187184456885833289',
> '8777189009399731927'} {code}
> To solve temporarily we routed outbound traffic to the private ip to public
> using iptables which resulted in successful outbound connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18560) Incorrect IP used for gossip across DCs with prefer_local=true
[
https://issues.apache.org/jira/browse/CASSANDRA-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18560:
-
Severity: Critical (was: Normal)
> Incorrect IP used for gossip across DCs with prefer_local=true
> --
>
> Key: CASSANDRA-18560
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18560
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
>Reporter: Brad Vernon
>Assignee: Brandon Williams
>Priority: Urgent
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> After installing a new node using 4.0.10 we experienced a situation where the
> new node attempted to connect to the private ip of a random number of nodes
> remote DCs which are only accessible via public ip for cross dc
> communications.
> The only impact was new nodes outbound connections, inbound from pre-4.0.10
> were not affected. system.peers_v2 (below) showed that the preferred_ip and
> preferred_port as null, only those in 4.0.10 nodes dc have perferred_ip
> values as expected.
> We believe the issue originated with
> https://issues.apache.org/jira/browse/CASSANDRA-16718
> Details on cluster:
> * All nodes have public IP configured as well as private IP
> * Listen/rpc addressrs are configured for private ip, broadcast is public IP
> * prefer_local=true is enabled for all nodes
> The log that showed the connection failing:
> {code:java}
> INFO [Messaging-EventLoop-3-8] 2023-06-01 00:14:21,565 NoSpamLogger.java:92
> -
> /99.81.:7000->/44.208.:7000-URGENT_MESSAGES-[no-channel]
> failed to connectio.netty.channel.ConnectTimeoutException: connection timed
> out: /10.26.5.11:7000 at
> io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe$2.run(AbstractEpollChannel.java:576){code}
> 99 and 44 instances can only access each other using public ips.
> gossipinfo output from 4.0.10 node
> {code:java}
> /44.208.
> generation:1661113358
> heartbeat:25267691
> LOAD:25267683:1.7882044268E10
> SCHEMA:24692061:e98b918d-499f-3ccc-8dbe-5af31f685bda
> DC:13:us-east-1
> RACK:15:1a
> RELEASE_VERSION:6:4.0.5
> NET_VERSION:2:12
> HOST_ID:3:9a41e668-060d-4cfe-bb1e-013f5116422d
> RPC_READY:1407:true
> INTERNAL_ADDRESS_AND_PORT:9:10.26.5.11:7000
> NATIVE_ADDRESS_AND_PORT:4:44.208.:9042
> STATUS_WITH_PORT:1393:NORMAL,-2262036356854762881
> SSTABLE_VERSIONS:7:big-nb
> TOKENS:1392: {code}
> Peers output from 4.0.10 node:
> {code:java}
>peer | peer_port | data_center | host_id
> | native_address | native_port | preferred_ip | preferred_port |
> rack | release_version | schema_version |
> tokens+---+-+--++-+--++--+-+--+---
> 44.208. | 7000 | us-east-1 |
> 9a41e668-060d-4cfe-bb1e-013f5116422d | 44.208. |9042 |
> null | null | 1a | 4.0.5 |
> e98b918d-499f-3ccc-8dbe-5af31f685bda |{'-2262036356854762881',
> '-4197710115038136897', '-7072386316096662315', '2085255826742630980',
> '249732489387853170', '4976300208126705818', '7187184456885833289',
> '8777189009399731927'} {code}
> To solve temporarily we routed outbound traffic to the private ip to public
> using iptables which resulted in successful outbound connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14667) Upgrade Dropwizard Metrics to 4.x
[ https://issues.apache.org/jira/browse/CASSANDRA-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733077#comment-17733077 ] Stefan Miklosovic commented on CASSANDRA-14667: --- [~e.dimitrova] any progress by any chance? > Upgrade Dropwizard Metrics to 4.x > - > > Key: CASSANDRA-14667 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14667 > Project: Cassandra > Issue Type: Task > Components: Observability/Metrics >Reporter: Stig Rohde Døssing >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > Attachments: signature.asc > > Time Spent: 20m > Remaining Estimate: 0h > > Cassandra currently uses Metrics 3.1.5. Version 4.0.0 added some fixes for > Java 9 compatibility. It would be good to upgrade the Metrics library as part > of the version of Cassandra that adds Java 9 compatibility > (https://issues.apache.org/jira/browse/CASSANDRA-9608). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18543) Waiting for gossip to settle does not wait for live endpoints
[ https://issues.apache.org/jira/browse/CASSANDRA-18543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18543: -- Fix Version/s: 3.11.16 4.0.11 4.1.3 5.0 (was: 3.11.x) (was: 5.x) (was: 4.0.x) (was: 4.1.x) Since Version: NA Source Control Link: https://github.com/apache/cassandra/commit/64d953fdcac91715898454a3cb04d932910a70b7 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Waiting for gossip to settle does not wait for live endpoints > - > > Key: CASSANDRA-18543 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18543 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Cameron Zemek >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.16, 4.0.11, 4.1.3, 5.0 > > Attachments: gossip.patch, gossip4.patch > > Time Spent: 40m > Remaining Estimate: 0h > > When a node starts it will get endpoint states (via shadow round) but have > all nodes marked as down. The problem is the wait to settle only checks the > size of endpoint states is stable before starting Native transport. Once > native transport starts it will receive queries and fail consistency levels > such as LOCAL_QUORUM since it still thinks nodes are down. > This is problem for a number of large clusters for our customers. The cluster > has quorum but due to this issue a node restart is causing a bunch of query > errors. > My initial solution to this was to only check live endpoints size in addition > to size of endpoint states. This worked but I noticed in testing this fix > that there also a lot of duplication of checking the same node (via Echo > messages) for liveness. So the patch also removes this duplication of > checking node is UP in markAlive. > The final problem I found while testing is sometimes could still not see a > change in live endpoints due to only 1 second polling, so the patch allows > for overridding the settle parameters. I could not reliability reproduce this > but think its worth providing a way to override these hardcoded values. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-3.11 updated (1eccb2bc1f -> 64d953fdca)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 1eccb2bc1f Fix error message handling when trying to use CLUSTERING ORDER with non-clustering column add 64d953fdca Wait for live endpoints in gossip waiting to settle No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + src/java/org/apache/cassandra/gms/Gossiper.java | 44 + 2 files changed, 38 insertions(+), 7 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (622397e7e5 -> 2b98d487d0)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 622397e7e5 Merge branch 'cassandra-4.0' into cassandra-4.1 add 64d953fdca Wait for live endpoints in gossip waiting to settle add 49dba85ec8 Merge branch 'cassandra-3.11' into cassandra-4.0 add 2b98d487d0 Merge branch 'cassandra-4.0' into cassandra-4.1 No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../config/CassandraRelevantProperties.java| 15 ++ src/java/org/apache/cassandra/gms/Gossiper.java| 57 +++--- 3 files changed, 65 insertions(+), 8 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (c37bcbf7e9 -> 49dba85ec8)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from c37bcbf7e9 Include TLSv1.2 in negotiatedProtocolMustBeAcceptedProtocolTest Add a comment about the use of disabled TLSv1.1 with JDK 8 and higher to negotiatedProtocolMustBeAcceptedProtocolTest add 64d953fdca Wait for live endpoints in gossip waiting to settle add 49dba85ec8 Merge branch 'cassandra-3.11' into cassandra-4.0 No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../config/CassandraRelevantProperties.java| 15 ++ src/java/org/apache/cassandra/gms/Gossiper.java| 57 +++--- 3 files changed, 65 insertions(+), 8 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository.
smiklosovic pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit c7260399d65dd84936a3ca85586b20a6b7ef009d
Merge: a55d4183f5 2b98d487d0
Author: Stefan Miklosovic
AuthorDate: Thu Jun 15 13:23:47 2023 +0200
Merge branch 'cassandra-4.1' into trunk
CHANGES.txt| 1 +
.../config/CassandraRelevantProperties.java| 16 +++
src/java/org/apache/cassandra/gms/Gossiper.java| 55 +++---
3 files changed, 65 insertions(+), 7 deletions(-)
diff --cc src/java/org/apache/cassandra/config/CassandraRelevantProperties.java
index 8eaaa7a9e0,23f9598964..fbb20766fa
--- a/src/java/org/apache/cassandra/config/CassandraRelevantProperties.java
+++ b/src/java/org/apache/cassandra/config/CassandraRelevantProperties.java
@@@ -161,153 -120,77 +161,169 @@@ public enum CassandraRelevantPropertie
* This property indicates whether SSL client authentication is enabled -
com.sun.management.jmxremote.ssl.need.client.auth.
* Default is set to false.
*/
-COM_SUN_MANAGEMENT_JMXREMOTE_SSL_NEED_CLIENT_AUTH
("com.sun.management.jmxremote.ssl.need.client.auth"),
-
+
COM_SUN_MANAGEMENT_JMXREMOTE_SSL_NEED_CLIENT_AUTH("com.sun.management.jmxremote.ssl.need.client.auth"),
+/** Defaults to false for 4.1 but plan to switch to true in a later
release the thinking is that environments
+ * may not work right off the bat so safer to add this feature disabled
by default */
+
CONFIG_ALLOW_SYSTEM_PROPERTIES("cassandra.config.allow_system_properties"),
+CONFIG_LOADER("cassandra.config.loader"),
+CONSISTENT_DIRECTORY_LISTINGS("cassandra.consistent_directory_listings"),
+CONSISTENT_RANGE_MOVEMENT("cassandra.consistent.rangemovement", "true"),
+
CONSISTENT_SIMULTANEOUS_MOVES_ALLOW("cassandra.consistent.simultaneousmoves.allow"),
+
CUSTOM_GUARDRAILS_CONFIG_PROVIDER_CLASS("cassandra.custom_guardrails_config_provider_class"),
+CUSTOM_QUERY_HANDLER_CLASS("cassandra.custom_query_handler_class"),
+CUSTOM_TRACING_CLASS("cassandra.custom_tracing_class"),
+/** Controls the type of bufffer (heap/direct) used for shared scratch
buffers */
+DATA_OUTPUT_BUFFER_ALLOCATE_TYPE("cassandra.dob.allocate_type"),
+
DATA_OUTPUT_STREAM_PLUS_TEMP_BUFFER_SIZE("cassandra.data_output_stream_plus_temp_buffer_size",
"8192"),
+
DECAYING_ESTIMATED_HISTOGRAM_RESERVOIR_STRIPE_COUNT("cassandra.dehr_stripe_count",
"2"),
+
DEFAULT_PROVIDE_OVERLAPPING_TOMBSTONES("default.provide.overlapping.tombstones"),
+/** determinism properties for testing */
+
DETERMINISM_SSTABLE_COMPRESSION_DEFAULT("cassandra.sstable_compression_default",
"true"),
+DETERMINISM_UNSAFE_UUID_NODE("cassandra.unsafe.deterministicuuidnode"),
+
DIAGNOSTIC_SNAPSHOT_INTERVAL_NANOS("cassandra.diagnostic_snapshot_interval_nanos",
"600"),
+
DISABLE_AUTH_CACHES_REMOTE_CONFIGURATION("cassandra.disable_auth_caches_remote_configuration"),
+/** properties to disable certain behaviours for testing */
+
DISABLE_GOSSIP_ENDPOINT_REMOVAL("cassandra.gossip.disable_endpoint_removal"),
+DISABLE_PAXOS_AUTO_REPAIRS("cassandra.disable_paxos_auto_repairs"),
+DISABLE_PAXOS_STATE_FLUSH("cassandra.disable_paxos_state_flush"),
+DISABLE_SSTABLE_ACTIVITY_TRACKING("cassandra.sstable_activity_tracking",
"true"),
+DISABLE_STCS_IN_L0("cassandra.disable_stcs_in_l0"),
+DISABLE_TCACTIVE_OPENSSL("cassandra.disable_tcactive_openssl"),
+/** property for the rate of the scheduled task that monitors disk usage
*/
+
DISK_USAGE_MONITOR_INTERVAL_MS("cassandra.disk_usage.monitor_interval_ms",
convertToString(TimeUnit.SECONDS.toMillis(30))),
+/** property for the interval on which the repeated client warnings and
diagnostic events about disk usage are ignored */
+DISK_USAGE_NOTIFY_INTERVAL_MS("cassandra.disk_usage.notify_interval_ms",
convertToString(TimeUnit.MINUTES.toMillis(30))),
+DOB_DOUBLING_THRESHOLD_MB("cassandra.DOB_DOUBLING_THRESHOLD_MB", "64"),
+DOB_MAX_RECYCLE_BYTES("cassandra.dob_max_recycle_bytes",
convertToString(1024 * 1024)),
/**
- * This property indicates the location for the access file. If
com.sun.management.jmxremote.authenticate is false,
- * then this property and the password and access files, are ignored.
Otherwise, the access file must exist and
- * be in the valid format. If the access file is empty or nonexistent,
then no access is allowed.
+ * When draining, how long to wait for mutating executors to shutdown.
*/
-COM_SUN_MANAGEMENT_JMXREMOTE_ACCESS_FILE
("com.sun.management.jmxremote.access.file"),
-
-/** This property indicates the path to the password file -
com.sun.management.jmxremote.password.file */
-COM_SUN_MANAGEMENT_JMXREMOTE_PASSWORD_FILE
("com.sun.management.jmxremote.password.
[cassandra] branch trunk updated (a55d4183f5 -> c7260399d6)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from a55d4183f5 Merge branch 'cassandra-4.1' into trunk add 64d953fdca Wait for live endpoints in gossip waiting to settle add 49dba85ec8 Merge branch 'cassandra-3.11' into cassandra-4.0 add 2b98d487d0 Merge branch 'cassandra-4.0' into cassandra-4.1 new c7260399d6 Merge branch 'cassandra-4.1' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt| 1 + .../config/CassandraRelevantProperties.java| 16 +++ src/java/org/apache/cassandra/gms/Gossiper.java| 55 +++--- 3 files changed, 65 insertions(+), 7 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (ac4d65cfe -> b51bcb773)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard ac4d65cfe generate docs for 8efdf127 new b51bcb773 generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (ac4d65cfe) \ N -- N -- N refs/heads/asf-staging (b51bcb773) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18602) UnknownColumnFamilyException reading from socket Error Post DB Version Upgrade from 3.11.10 to 4.1.0
[ https://issues.apache.org/jira/browse/CASSANDRA-18602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732996#comment-17732996 ] Brandon Williams commented on CASSANDRA-18602: -- Without a clear reproduction or more thorough information to determine a bug, I don't think there is anything actionable from a development standpoint here, and this jira is for the development of Apache Cassandra and thus makes a poor vehicle for support, which seems more appropriate for the position this is in. I recommend contacting the community for support on slack or the ML: https://cassandra.apache.org/_/community.html If after that there is clear agency for development, please do come back with your supplemental findings. > UnknownColumnFamilyException reading from socket Error Post DB Version > Upgrade from 3.11.10 to 4.1.0 > - > > Key: CASSANDRA-18602 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18602 > Project: Cassandra > Issue Type: Bug >Reporter: Aman Paliwal >Priority: Normal > > There is a three Node Apache Cassandra Cluster with version: 3.11.10 with > around 160GB data on each node and Keyspace RF is 3 > On Day1, On first Node, DB Version was Upgraded from 3.11.10 to 4.1.0 and > upgradesstables was run post start of db service from apache cassandra 4.1.0 > binaries. > On Day2, On Second Node, Post start of binaries from 4.1.0, On third node > which was with DB Version 3.11.10 below error was continuously observed. > When cfId d46780c2-2f1c-3db9-b4c1-b8d9fbc0cc23 was checked it was of Table > system_auth.network_permissions > > /* > WARN [MessagingService-Incoming-/10.x.135.y] 2023-06-10 03:11:37,632 > IncomingTcpConnection.java:107 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId d46780c2-2f1c-3db9-b4c1-b8d9fbc0cc23. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > WARN [MessagingService-Incoming-/10.x.135.y] 2023-06-10 03:15:47,633 > IncomingTcpConnection.java:107 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId d46780c2-2f1c-3db9-b4c1-b8d9fbc0cc23. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > WARN [MessagingService-Incoming-/10.x.135.y] 2023-06-10 03:19:57,638 > IncomingTcpConnection.java:107 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId d46780c2-2f1c-3db9-b4c1-b8d9fbc0cc23. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > WARN [MessagingService-Incoming-/10.x.135.y] 2023-06-10 03:19:57,642 > IncomingTcpConnection.java:107 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId d46780c2-2f1c-3db9-b4c1-b8d9fbc0cc23. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > WARN [MessagingService-Incoming-/10.x.135.y] 2023-06-10 03:28:17,643 > IncomingTcpConnection.java:107 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId d46780c2-2f1c-3db9-b4c1-b8d9fbc0cc23. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > WARN [MessagingService-Incoming-/10.x.135.y] 2023-06-10 03:28:17,649 > IncomingTcpConnection.java:107 - UnknownColumnFamilyException reading from > socket; closing > */ > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18593) CircleCI: Add separate approval step for oa utests on separate workflows
[
https://issues.apache.org/jira/browse/CASSANDRA-18593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732948#comment-17732948
]
Berenguer Blasi commented on CASSANDRA-18593:
-
LGTM +1
> CircleCI: Add separate approval step for oa utests on separate workflows
>
>
> Key: CASSANDRA-18593
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18593
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CASSANDRA-14227 added new {{j*_utests_oa}} jobs to run unit tests with the
> new, not-default "oa" sstable format. Those tests depend on the
> {{start_j*_unit_tests}} approval step on the separate workflows.
> However, the separate workflow is meant to allow running jobs individually,
> and having a common approval step for both {{j*_unit_tests}} and
> {{j*_utests_oa}} prevents us from doing so. That's the case for example of
> the development of CASSANDRA-18504, where I want to run a single unit test
> job without caring about the specialization, but the common approval step
> forces me to run both jobs, duplicating the costs. An example run can be seen
> [here|https://app.circleci.com/pipelines/github/adelapena/cassandra/2948/workflows/67e5bfcd-c8df-4558-a889-c8828e8dd310].
> I think that {{j*_utests_oa}} should have its own separate approval step, the
> same way that {{{}j*_utest_cdc{}}}, {{{}j*_utest_fqltool{}}},
> {{j*_utest_compression}} or {{j*_utest_system_keyspace_directory}} have their
> own approval step.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18596) Assertion error when describing mv as table
[
https://issues.apache.org/jira/browse/CASSANDRA-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maciej Sokol updated CASSANDRA-18596:
-
Test and Documentation Plan: Unittest included.
Status: Patch Available (was: Open)
> Assertion error when describing mv as table
> ---
>
> Key: CASSANDRA-18596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18596
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Maciej Sokol
>Assignee: Maciej Sokol
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When describing materialized view as a table Cassandra gets an assertion
> error.
> Steps to reproduce:
> CREATE KEYSPACE test WITH replication = \{'class': 'NetworkTopologyStrategy',
> 'datacenter1': '3'} AND durable_writes = true;
> CREATE TABLE test.table1 (key1 text,key2 int,value int,PRIMARY KEY (key1,
> key2));
> CREATE MATERIALIZED VIEW test.table1_by_value AS SELECT key1, key2, value
> FROM test.table1 WHERE value IS NOT NULL AND key1 IS NOT NULL AND key2 IS NOT
> NULL PRIMARY KEY(value, key1, key2);
> DESCRIBE MATERIALIZED VIEW test.table1;
> DESCRIBE TABLE test.table1_by_value;
> DESCRIBE TABLE test.non_existing;
>
> From the above the "DESCRIBE TABLE test.table1_by_value;" throws an assertion
> error while "DESCRIBE TABLE test.non_existing;" returns a meaningful error
> msg.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18596) Assertion error when describing mv as table
[
https://issues.apache.org/jira/browse/CASSANDRA-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maciej Sokol updated CASSANDRA-18596:
-
Test and Documentation Plan: Unittest included, see linked PRs (was:
Unittest included.)
> Assertion error when describing mv as table
> ---
>
> Key: CASSANDRA-18596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18596
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Maciej Sokol
>Assignee: Maciej Sokol
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When describing materialized view as a table Cassandra gets an assertion
> error.
> Steps to reproduce:
> CREATE KEYSPACE test WITH replication = \{'class': 'NetworkTopologyStrategy',
> 'datacenter1': '3'} AND durable_writes = true;
> CREATE TABLE test.table1 (key1 text,key2 int,value int,PRIMARY KEY (key1,
> key2));
> CREATE MATERIALIZED VIEW test.table1_by_value AS SELECT key1, key2, value
> FROM test.table1 WHERE value IS NOT NULL AND key1 IS NOT NULL AND key2 IS NOT
> NULL PRIMARY KEY(value, key1, key2);
> DESCRIBE MATERIALIZED VIEW test.table1;
> DESCRIBE TABLE test.table1_by_value;
> DESCRIBE TABLE test.non_existing;
>
> From the above the "DESCRIBE TABLE test.table1_by_value;" throws an assertion
> error while "DESCRIBE TABLE test.non_existing;" returns a meaningful error
> msg.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18596) Assertion error when describing mv as table
[
https://issues.apache.org/jira/browse/CASSANDRA-18596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732908#comment-17732908
]
Maciej Sokol commented on CASSANDRA-18596:
--
The patch merges cleanly to 4.1 and trunk. If someone could run CI that would
be great.
> Assertion error when describing mv as table
> ---
>
> Key: CASSANDRA-18596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18596
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
>Reporter: Maciej Sokol
>Assignee: Maciej Sokol
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When describing materialized view as a table Cassandra gets an assertion
> error.
> Steps to reproduce:
> CREATE KEYSPACE test WITH replication = \{'class': 'NetworkTopologyStrategy',
> 'datacenter1': '3'} AND durable_writes = true;
> CREATE TABLE test.table1 (key1 text,key2 int,value int,PRIMARY KEY (key1,
> key2));
> CREATE MATERIALIZED VIEW test.table1_by_value AS SELECT key1, key2, value
> FROM test.table1 WHERE value IS NOT NULL AND key1 IS NOT NULL AND key2 IS NOT
> NULL PRIMARY KEY(value, key1, key2);
> DESCRIBE MATERIALIZED VIEW test.table1;
> DESCRIBE TABLE test.table1_by_value;
> DESCRIBE TABLE test.non_existing;
>
> From the above the "DESCRIBE TABLE test.table1_by_value;" throws an assertion
> error while "DESCRIBE TABLE test.non_existing;" returns a meaningful error
> msg.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (8cf1ecae4 -> ac4d65cfe)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 8cf1ecae4 generate docs for 1b144e50 add 8efdf1270 github action to generate website new ac4d65cfe generate docs for 8efdf127 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8cf1ecae4) \ N -- N -- N refs/heads/asf-staging (ac4d65cfe) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .github/workflows/site-content.yaml | 47 content/search-index.js | 2 +- site-ui/Dockerfile | 2 ++ site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 4 files changed, 50 insertions(+), 1 deletion(-) create mode 100644 .github/workflows/site-content.yaml - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (85f0a9db5 -> 8cf1ecae4)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 85f0a9db5 generate docs for 1b144e50 new 8cf1ecae4 generate docs for 1b144e50 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (85f0a9db5) \ N -- N -- N refs/heads/asf-staging (8cf1ecae4) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4796900 -> 4796900 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk_generated created (now b88f547cc)
This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch trunk_generated in repository https://gitbox.apache.org/repos/asf/cassandra-website.git at b88f547cc generate (top-level-only) docs for 8efdf12 This branch includes the following new commits: new b88f547cc generate (top-level-only) docs for 8efdf12 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: github action to generate website
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new 8efdf1270 github action to generate website 8efdf1270 is described below commit 8efdf1270c2000b968fe8313a07babde3c2f7dd2 Author: mck AuthorDate: Sun Jul 18 14:17:50 2021 +0200 github action to generate website --- .github/workflows/site-content.yaml | 47 + site-ui/Dockerfile | 2 ++ 2 files changed, 49 insertions(+) diff --git a/.github/workflows/site-content.yaml b/.github/workflows/site-content.yaml new file mode 100644 index 0..bdb3c82c4 --- /dev/null +++ b/.github/workflows/site-content.yaml @@ -0,0 +1,47 @@ +# +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# + +name: Build toplevel website + +on: + push: +paths: + - 'site-*/**' + release: +types: + - published + +jobs: + cassandra-website-content: +runs-on: ubuntu-latest + +steps: + +- uses: actions/checkout@v3 + +- name: Build Website + run: | +git config --global user.email "g...@cassandra.apache.org" +git config --global user.name "GHA for Apache Cassandra Website" +git switch -C $(git rev-parse --abbrev-ref HEAD)_generated +./run.sh website-ui bundle -a BUILD_USER_ARG:$(whoami) -a UID_ARG:$(id -u) -a GID_ARG:$(id -g) +./run.sh website container -a BUILD_USER_ARG:$(whoami) -a UID_ARG:$(id -u) -a GID_ARG:$(id -g) +./run.sh website build +git add content +git commit -am "generate (top-level-only) docs for `git rev-parse --short HEAD`" +git push -f --set-upstream origin $(git rev-parse --abbrev-ref HEAD) diff --git a/site-ui/Dockerfile b/site-ui/Dockerfile index bda86949a..b7ea6246e 100644 --- a/site-ui/Dockerfile +++ b/site-ui/Dockerfile @@ -1,4 +1,5 @@ FROM ubuntu:18.04 +# # Set up non-root user, 'build', with default uid:gid # This allows passing --build-arg to use localhost username, and uid:gid: # $ docker build \ @@ -10,6 +11,7 @@ FROM ubuntu:18.04 # # Other container parameters can be overridden at build time as well: # - NODE_VERSION_ARG: Version of node to use. +# ARG BUILD_USER_ARG="build" ARG UID_ARG=1000 ARG GID_ARG=1000 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
