[jira] [Commented] (CASSANDRA-14269) The Data Modeling section of the web site is empty
[ https://issues.apache.org/jira/browse/CASSANDRA-14269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377714#comment-16377714 ] Michael Mior commented on CASSANDRA-14269: -- A few resources that someone wanting to tackle this may want to look at: https://www.datastax.com/dev/blog/basic-rules-of-cassandra-data-modeling https://www.ebayinc.com/stories/blogs/tech/cassandra-data-modeling-best-practices-part-1/ https://www.ebayinc.com/stories/blogs/tech/cassandra-data-modeling-best-practices-part-2/ > The Data Modeling section of the web site is empty > -- > > Key: CASSANDRA-14269 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14269 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Kenneth Brotman >Priority: Major > > [http://cassandra.apache.org/doc/latest/data_modeling/index.html] > is empty. Please submit content. Myself or someone else will take it from > there. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14263) The home page of Cassandra is mobile friendly but the link to the third parties is not
[ https://issues.apache.org/jira/browse/CASSANDRA-14263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377608#comment-16377608 ] Michael Mior commented on CASSANDRA-14263: -- For me some of the logos get cut off but otherwise, the page is quite readable. It might be nice to fix, but I don't think it makes a big difference. (This is assuming others aren't seeing worse issues in other mobile browsers.) > The home page of Cassandra is mobile friendly but the link to the third > parties is not > -- > > Key: CASSANDRA-14263 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14263 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Kenneth Brotman >Priority: Major > > Near the bottom the home page of the Apache Cassandra web site: > [http://cassandra.apache.org/] > is a link to third parties who professionally support Cassandra. > The home page of Cassandra is mobile friendly but the link to the third > parties is not: > [https://wiki.apache.org/cassandra/ThirdPartySupport] > Any suggestions? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12044) Materialized view definition regression in clustering key
[
https://issues.apache.org/jira/browse/CASSANDRA-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342350#comment-15342350
]
Michael Mior commented on CASSANDRA-12044:
--
As an aside, the error message should probably change since it says "partition
key" instead of "primary key."
> Materialized view definition regression in clustering key
> -
>
> Key: CASSANDRA-12044
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12044
> Project: Cassandra
> Issue Type: Bug
>Reporter: Michael Mior
>Assignee: Carl Yeksigian
>
> This bug was reported on the
> [users|https://mail-archives.apache.org/mod_mbox/cassandra-user/201606.mbox/%3CCAG0vsSJRtRjLJqKsd3M8X-8nXpPwRj7Q80mNkuy8sy%2B%2B%3D%2BocHA%40mail.gmail.com%3E]
> mailing list. The following definitions work in 3.0.3 but fail in 3.0.7.
> {code}
> CREATE TABLE ks.pa (
> id bigint,
> sub_id text,
> name text,
> class text,
> r_id bigint,
> k_id bigint,
> created timestamp,
> priority int,
> updated timestamp,
> value text,
> PRIMARY KEY (id, sub_id, name)
> );
> CREATE ks.mv_pa AS
> SELECT k_id, name, value, sub_id, id, class, r_id
> FROM ks.pa
> WHERE k_id IS NOT NULL AND name IS NOT NULL AND value IS NOT NULL AND
> sub_id IS NOT NULL AND id IS NOT NULL
> PRIMARY KEY ((k_id, name), value, sub_id, id);
> {code}
> After running bisect, I've narrowed it down to commit
> [86ba227|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=86ba227477b9f8595eb610ecaf950cfbc29dd36b]
> from [CASSANDRA-11475|https://issues.apache.org/jira/browse/CASSANDRA-11475].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12044) Materialized view definition regression in clustering key
[
https://issues.apache.org/jira/browse/CASSANDRA-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342348#comment-15342348
]
Michael Mior commented on CASSANDRA-12044:
--
Thanks for clarifying. This makes a lot of sense.
> Materialized view definition regression in clustering key
> -
>
> Key: CASSANDRA-12044
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12044
> Project: Cassandra
> Issue Type: Bug
>Reporter: Michael Mior
>Assignee: Carl Yeksigian
>
> This bug was reported on the
> [users|https://mail-archives.apache.org/mod_mbox/cassandra-user/201606.mbox/%3CCAG0vsSJRtRjLJqKsd3M8X-8nXpPwRj7Q80mNkuy8sy%2B%2B%3D%2BocHA%40mail.gmail.com%3E]
> mailing list. The following definitions work in 3.0.3 but fail in 3.0.7.
> {code}
> CREATE TABLE ks.pa (
> id bigint,
> sub_id text,
> name text,
> class text,
> r_id bigint,
> k_id bigint,
> created timestamp,
> priority int,
> updated timestamp,
> value text,
> PRIMARY KEY (id, sub_id, name)
> );
> CREATE ks.mv_pa AS
> SELECT k_id, name, value, sub_id, id, class, r_id
> FROM ks.pa
> WHERE k_id IS NOT NULL AND name IS NOT NULL AND value IS NOT NULL AND
> sub_id IS NOT NULL AND id IS NOT NULL
> PRIMARY KEY ((k_id, name), value, sub_id, id);
> {code}
> After running bisect, I've narrowed it down to commit
> [86ba227|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=86ba227477b9f8595eb610ecaf950cfbc29dd36b]
> from [CASSANDRA-11475|https://issues.apache.org/jira/browse/CASSANDRA-11475].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12044) Materialized view definition regression in clustering key
[
https://issues.apache.org/jira/browse/CASSANDRA-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341710#comment-15341710
]
Michael Mior commented on CASSANDRA-12044:
--
The patch below seems to fix things. Just waiting for the test suite to run and
need to add a test for this particular case.
{code}
commit 0bd763efb0a31d05cbb61427b8828df73b957164
Author: Michael Mior
Date: Tue Jun 21 08:47:25 2016 -0400
Fix check for valid MV PKs
diff --git
a/src/java/org/apache/cassandra/cql3/statements/CreateViewStatement.java
b/src/java/org/apache/cassandra/cql3/statements/Cr
index 6446602..951dedd 100644
--- a/src/java/org/apache/cassandra/cql3/statements/CreateViewStatement.java
+++ b/src/java/org/apache/cassandra/cql3/statements/CreateViewStatement.java
@@ -315,7 +315,8 @@ public class CreateViewStatement extends
SchemaAlteringStatement
ColumnDefinition def = cfm.getColumnDefinition(identifier);
boolean isPk = basePK.contains(identifier);
-if (!isPk && hasNonPKColumn)
+if (!isPk && hasNonPKColumn
+&& cfm.getColumnDefinition(identifier).isPartitionKey())
throw new InvalidRequestException(String.format("Cannot include
more than one non-primary key column '%s' in materialized
// We don't need to include the "IS NOT NULL" filter on a
non-composite partition key
{code}
> Materialized view definition regression in clustering key
> -
>
> Key: CASSANDRA-12044
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12044
> Project: Cassandra
> Issue Type: Bug
>Reporter: Michael Mior
>
> This bug was reported on the
> [users|https://mail-archives.apache.org/mod_mbox/cassandra-user/201606.mbox/%3CCAG0vsSJRtRjLJqKsd3M8X-8nXpPwRj7Q80mNkuy8sy%2B%2B%3D%2BocHA%40mail.gmail.com%3E]
> mailing list. The following definitions work in 3.0.3 but fail in 3.0.7.
> {code}
> CREATE TABLE ks.pa (
> id bigint,
> sub_id text,
> name text,
> class text,
> r_id bigint,
> k_id bigint,
> created timestamp,
> priority int,
> updated timestamp,
> value text,
> PRIMARY KEY (id, sub_id, name)
> );
> CREATE ks.mv_pa AS
> SELECT k_id, name, value, sub_id, id, class, r_id
> FROM ks.pa
> WHERE k_id IS NOT NULL AND name IS NOT NULL AND value IS NOT NULL AND
> sub_id IS NOT NULL AND id IS NOT NULL
> PRIMARY KEY ((k_id, name), value, sub_id, id);
> {code}
> After running bisect, I've narrowed it down to commit
> [86ba227|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=86ba227477b9f8595eb610ecaf950cfbc29dd36b]
> from [CASSANDRA-11475|https://issues.apache.org/jira/browse/CASSANDRA-11475].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-12044) Materialized view definition regression in clustering key
Michael Mior created CASSANDRA-12044:
Summary: Materialized view definition regression in clustering key
Key: CASSANDRA-12044
URL: https://issues.apache.org/jira/browse/CASSANDRA-12044
Project: Cassandra
Issue Type: Bug
Reporter: Michael Mior
This bug was reported on the
[users|https://mail-archives.apache.org/mod_mbox/cassandra-user/201606.mbox/%3CCAG0vsSJRtRjLJqKsd3M8X-8nXpPwRj7Q80mNkuy8sy%2B%2B%3D%2BocHA%40mail.gmail.com%3E]
mailing list. The following definitions work in 3.0.3 but fail in 3.0.7.
{code}
CREATE TABLE ks.pa (
id bigint,
sub_id text,
name text,
class text,
r_id bigint,
k_id bigint,
created timestamp,
priority int,
updated timestamp,
value text,
PRIMARY KEY (id, sub_id, name)
);
CREATE ks.mv_pa AS
SELECT k_id, name, value, sub_id, id, class, r_id
FROM ks.pa
WHERE k_id IS NOT NULL AND name IS NOT NULL AND value IS NOT NULL AND
sub_id IS NOT NULL AND id IS NOT NULL
PRIMARY KEY ((k_id, name), value, sub_id, id);
{code}
After running bisect, I've narrowed it down to commit
[86ba227|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=86ba227477b9f8595eb610ecaf950cfbc29dd36b]
from [CASSANDRA-11475|https://issues.apache.org/jira/browse/CASSANDRA-11475].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12021) Consider removing Util.toString
[
https://issues.apache.org/jira/browse/CASSANDRA-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Mior resolved CASSANDRA-12021.
--
Resolution: Invalid
Very sorry. My default project appears to have changed. This issue is not for
Cassandra.
> Consider removing Util.toString
> ---
>
> Key: CASSANDRA-12021
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12021
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Michael Mior
>Priority: Minor
>
> {{Util.toString}} seems unnecessary in light of
> {{com.google.common.base.Joiner}}. There are ~16 total usages of this across
> the entire code base. One inside SubstitutionVisitor and the rest scattered
> around the Mongo, Cassandra, and Elasticsearch adapters. If there are no
> objections, I'll remove this and replace with {{Joiner}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-12021) Consider removing Util.toString
Michael Mior created CASSANDRA-12021:
Summary: Consider removing Util.toString
Key: CASSANDRA-12021
URL: https://issues.apache.org/jira/browse/CASSANDRA-12021
Project: Cassandra
Issue Type: Improvement
Reporter: Michael Mior
Priority: Minor
{{Util.toString}} seems unnecessary in light of
{{com.google.common.base.Joiner}}. There are ~16 total usages of this across
the entire code base. One inside SubstitutionVisitor and the rest scattered
around the Mongo, Cassandra, and Elasticsearch adapters. If there are no
objections, I'll remove this and replace with {{Joiner}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8859) CollationController not using collectTimeOrderedData
[
https://issues.apache.org/jira/browse/CASSANDRA-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335511#comment-14335511
]
Michael Mior commented on CASSANDRA-8859:
-
Thanks for clarifying! Is there a simple example of a scenario where the
{{collectTimeOrderedData}} code path will be used?
CollationController not using collectTimeOrderedData
Key: CASSANDRA-8859
URL: https://issues.apache.org/jira/browse/CASSANDRA-8859
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Michael Mior
Priority: Minor
I'd appreciate some help with a Cassandra 2.1.2 issue I'm experiencing. I'm
running a query which looks like this:
{code}
CREATE TABLE single_row_fetch (id uuid PRIMARY KEY, data text)
SELECT data FROM single_row_fetch WHERE id = ?
{code}
When writing test data into this table, I disabled compaction. I then wrote
data for performed a flush, and then overwrote the data, and so on. I varied
the number of times the data was overwritten and flushed. This has the effect
of controlling the number of SSTables. However, given that the table only has
one non-key row, only a single SSTable will ever have the most recent data
for this row. I confirmed that the expected number of SSTables were generated
and the timestamps of the are as expected.
However, when I run the query with tracing, I see that Cassandra still reads
from ALL of the SSTables via {{collectAllData}} in {{CollationController}}.
Given that this query only fetches a single column, I would expect this query
to take the {{collectTimeOrderedData}} code path and then only examine the
first SSTable after seeing that it contains the relevant data.
Any insights on why this is the case and it what situations I would get the
expected behaviour would be incredibly helpful!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-8859) CollationController not using collectTimeOrderedData
Michael Mior created CASSANDRA-8859:
---
Summary: CollationController not using collectTimeOrderedData
Key: CASSANDRA-8859
URL: https://issues.apache.org/jira/browse/CASSANDRA-8859
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Michael Mior
Priority: Minor
I'd appreciate some help with a Cassandra 2.1.2 issue I'm experiencing. I'm
running a query which looks like this:
{code}
CREATE TABLE single_row_fetch (id uuid PRIMARY KEY, data text)
SELECT data FROM single_row_fetch WHERE id = ?
{code}
When writing test data into this table, I disabled compaction. I then wrote
data for performed a flush, and then overwrote the data, and so on. I varied
the number of times the data was overwritten and flushed. This has the effect
of controlling the number of SSTables. However, given that the table only has
one non-key row, only a single SSTable will ever have the most recent data for
this row. I confirmed that the expected number of SSTables were generated and
the timestamps of the are as expected.
However, when I run the query with tracing, I see that Cassandra still reads
from ALL of the SSTables via {{collectAllData}} in {{CollationController}}.
Given that this query only fetches a single column, I would expect this query
to take the {{collectTimeOrderedData}} code path and then only examine the
first SSTable after seeing that it contains the relevant data.
Any insights on why this is the case and it what situations I would get the
expected behaviour would be incredibly helpful!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8859) CollationController not using collectTimeOrderedData
[
https://issues.apache.org/jira/browse/CASSANDRA-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335533#comment-14335533
]
Michael Mior commented on CASSANDRA-8859:
-
That is, in Cassandra 2.1.2. I understand that the scenario I mentioned above
will use this code path in 3.0.
CollationController not using collectTimeOrderedData
Key: CASSANDRA-8859
URL: https://issues.apache.org/jira/browse/CASSANDRA-8859
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Michael Mior
Priority: Minor
I'd appreciate some help with a Cassandra 2.1.2 issue I'm experiencing. I'm
running a query which looks like this:
{code}
CREATE TABLE single_row_fetch (id uuid PRIMARY KEY, data text)
SELECT data FROM single_row_fetch WHERE id = ?
{code}
When writing test data into this table, I disabled compaction. I then wrote
data for performed a flush, and then overwrote the data, and so on. I varied
the number of times the data was overwritten and flushed. This has the effect
of controlling the number of SSTables. However, given that the table only has
one non-key row, only a single SSTable will ever have the most recent data
for this row. I confirmed that the expected number of SSTables were generated
and the timestamps of the are as expected.
However, when I run the query with tracing, I see that Cassandra still reads
from ALL of the SSTables via {{collectAllData}} in {{CollationController}}.
Given that this query only fetches a single column, I would expect this query
to take the {{collectTimeOrderedData}} code path and then only examine the
first SSTable after seeing that it contains the relevant data.
Any insights on why this is the case and it what situations I would get the
expected behaviour would be incredibly helpful!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
