[jira] [Updated] (CASSANDRA-18228) Reorganize Apache C* docs in trunk branch to match the IA
[ https://issues.apache.org/jira/browse/CASSANDRA-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18228: --- Reviewers: Michael Semb Wever, Stefan Miklosovic (was: Michael Semb Wever) > Reorganize Apache C* docs in trunk branch to match the IA > - > > Key: CASSANDRA-18228 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18228 > Project: Cassandra > Issue Type: New Feature > Components: Documentation >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Fix For: 5.x > > > An agreed-upon Information Architecture will be used to reorganize the C* 5.0 > docs. > IA doc: > https://docs.google.com/document/d/1A96K73vj9MbJoD7wJNgIKWrOkLq-ZL2cNZAEXSWrciY/edit?usp=sharing -- 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-18228) Reorganize Apache C* docs in trunk branch to match the IA
[ https://issues.apache.org/jira/browse/CASSANDRA-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18228: --- Status: Ready to Commit (was: Review In Progress) > Reorganize Apache C* docs in trunk branch to match the IA > - > > Key: CASSANDRA-18228 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18228 > Project: Cassandra > Issue Type: New Feature > Components: Documentation >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Fix For: 5.x > > > An agreed-upon Information Architecture will be used to reorganize the C* 5.0 > docs. > IA doc: > https://docs.google.com/document/d/1A96K73vj9MbJoD7wJNgIKWrOkLq-ZL2cNZAEXSWrciY/edit?usp=sharing -- 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 trunk updated: Reorganizing doc directories using new info arch
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.git
The following commit(s) were added to refs/heads/trunk by this push:
new 998a98eae8 Reorganizing doc directories using new info arch
998a98eae8 is described below
commit 998a98eae8317d85f5ba425cfd33b2ba975a20d9
Author: Lorina Poland
AuthorDate: Tue Feb 28 19:19:50 2023 -0800
Reorganizing doc directories using new info arch
patch by Lorina Poland; reviewed by Mick Semb Wever, Štefan Miklošovič for
CASSANDRA-18228
---
NEWS.txt | 2 +-
README.asc | 2 +-
conf/cassandra.yaml| 2 +-
doc/modules/ROOT/pages/index.adoc | 16 +-
doc/modules/cassandra/nav.adoc | 141
.../cassandra/pages/architecture/index.adoc| 2 +-
.../{storage_engine.adoc => storage-engine.adoc} | 0
.../cassandra/pages/cql/dynamic_data_masking.adoc | 178 -
.../cassandra/pages/data_modeling/index.adoc | 11 --
.../cassandra/pages/{ => developing}/cql/SASI.adoc | 0
.../pages/{ => developing}/cql/appendices.adoc | 0
.../pages/{ => developing}/cql/changes.adoc| 0
.../pages/{ => developing}/cql/cql_singlefile.adoc | 0
.../cassandra/pages/{ => developing}/cql/ddl.adoc | 0
.../pages/{ => developing}/cql/definitions.adoc| 0
.../cassandra/pages/{ => developing}/cql/dml.adoc | 0
.../pages/{ => developing}/cql/functions.adoc | 0
.../pages/{ => developing}/cql/index.adoc | 0
.../pages/{ => developing}/cql/indexes.adoc| 0
.../cassandra/pages/{ => developing}/cql/json.adoc | 0
.../cassandra/pages/{ => developing}/cql/mvs.adoc | 0
.../pages/{ => developing}/cql/operators.adoc | 0
.../pages/{ => developing}/cql/security.adoc | 0
.../pages/{ => developing}/cql/triggers.adoc | 0
.../pages/{ => developing}/cql/types.adoc | 0
.../data-modeling/data-modeling_conceptual.adoc} | 2 +-
.../data-modeling/data-modeling_logical.adoc} | 6 +-
.../data-modeling/data-modeling_physical.adoc} | 6 +-
.../data-modeling/data-modeling_queries.adoc} | 2 +-
.../data-modeling/data-modeling_rdbms.adoc}| 2 +-
.../data-modeling/data-modeling_refining.adoc} | 2 +-
.../data-modeling/data-modeling_schema.adoc} | 0
.../data-modeling/data-modeling_tools.adoc}| 0
.../data-modeling}/images/Figure_1_data_model.jpg | Bin
.../data-modeling}/images/Figure_2_data_model.jpg | Bin
.../images/data_modeling_chebotko_logical.png | Bin
.../images/data_modeling_chebotko_physical.png | Bin
.../images/data_modeling_hotel_bucketing.png | Bin
.../images/data_modeling_hotel_erd.png | Bin
.../images/data_modeling_hotel_logical.png | Bin
.../images/data_modeling_hotel_physical.png| Bin
.../images/data_modeling_hotel_queries.png | Bin
.../images/data_modeling_hotel_relational.png | Bin
.../images/data_modeling_reservation_logical.png | Bin
.../images/data_modeling_reservation_physical.png | Bin
.../pages/developing/data-modeling/index.adoc | 11 ++
.../data-modeling}/intro.adoc | 0
.../configuring.adoc | 0
.../drivers.adoc | 0
.../cassandra/pages/getting-started/index.adoc | 30
.../production.adoc| 0
.../querying.adoc | 2 +-
.../quickstart.adoc| 0
.../cassandra/pages/getting_started/index.adoc | 30
.../installing.adoc| 4 +-
.../pages/{ => integrating}/plugins/index.adoc | 0
.../configuration/cass_cl_archive_file.adoc| 0
.../configuration/cass_env_sh_file.adoc| 0
.../configuration/cass_jvm_options_file.adoc | 0
.../configuration/cass_logback_xml_file.adoc | 0
.../configuration/cass_rackdc_file.adoc| 0
.../configuration/cass_topo_file.adoc | 0
.../configuration/configuration.adoc | 0
.../pages/{ => managing}/configuration/index.adoc | 0
.../{ => managing}/operating/audit_logging.adoc| 0
.../{ => managing}/operating/auditlogging.adoc | 0
.../pages/{ => managing}/operating/backups.adoc| 0
.../{ => managing}/operating/bloom_filters.adoc| 0
.../{ => managing}/operating/bulk_loading.adoc | 0
.../pages/{ => managing}/operating/cdc.adoc| 0
.../{ => managing}/operating/compaction/index.adoc | 0
.../{ => managing}/operating/compaction/lcs.adoc | 0
.../{ => managing}/operating/compaction/stcs.adoc | 0
.../{ => managing}/operating/compaction/twcs.adoc | 0
[jira] [Updated] (CASSANDRA-18228) Reorganize Apache C* docs in trunk branch to match the IA
[ https://issues.apache.org/jira/browse/CASSANDRA-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-18228: --- Fix Version/s: 5.0 (was: 5.x) Source Control Link: https://github.com/apache/cassandra/commit/998a98eae8317d85f5ba425cfd33b2ba975a20d9 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [998a98eae8317d85f5ba425cfd33b2ba975a20d9 |https://github.com/apache/cassandra/commit/998a98eae8317d85f5ba425cfd33b2ba975a20d9]. > Reorganize Apache C* docs in trunk branch to match the IA > - > > Key: CASSANDRA-18228 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18228 > Project: Cassandra > Issue Type: New Feature > Components: Documentation >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Fix For: 5.0 > > > An agreed-upon Information Architecture will be used to reorganize the C* 5.0 > docs. > IA doc: > https://docs.google.com/document/d/1A96K73vj9MbJoD7wJNgIKWrOkLq-ZL2cNZAEXSWrciY/edit?usp=sharing -- 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-4.0 updated (b183e1f0de -> 1929550fc0)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from b183e1f0de Merge branch 'cassandra-3.11' into cassandra-4.0 new 90d0857d34 fix typos in data modeling and getting started docs new 1929550fc0 Merge branch 'cassandra-3.11' into cassandra-4.0 The 2 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: doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc | 2 +- doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc | 2 +- doc/modules/cassandra/pages/getting_started/production.adoc | 2 +- 3 files changed, 3 insertions(+), 3 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 (1a72fbd9c6 -> cfabddcfb0)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 1a72fbd9c6 Merge branch 'cassandra-4.0' into cassandra-4.1 new 90d0857d34 fix typos in data modeling and getting started docs new 1929550fc0 Merge branch 'cassandra-3.11' into cassandra-4.0 new cfabddcfb0 Merge branch 'cassandra-4.0' into cassandra-4.1 The 3 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: doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc | 2 +- doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc | 2 +- doc/modules/cassandra/pages/getting_started/production.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (998a98eae8 -> d7314a5988)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 998a98eae8 Reorganizing doc directories using new info arch new 90d0857d34 fix typos in data modeling and getting started docs new 1929550fc0 Merge branch 'cassandra-3.11' into cassandra-4.0 new cfabddcfb0 Merge branch 'cassandra-4.0' into cassandra-4.1 new d7314a5988 Merge branch 'cassandra-4.1' into trunk The 4 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: - 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: fix typos in data modeling and getting started docs
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-3.11 by this push: new 90d0857d34 fix typos in data modeling and getting started docs 90d0857d34 is described below commit 90d0857d341a1735edfa9450c4488372b3b44f87 Author: Steve Putala AuthorDate: Mon Apr 17 22:18:58 2023 -0400 fix typos in data modeling and getting started docs patch by Steve Putala; reviewed by Mick Semb Wever ref: https://github.com/apache/cassandra/pull/2280 --- doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc | 2 +- doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc | 2 +- doc/modules/cassandra/pages/getting_started/production.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc b/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc index 21f9801812..ed40fb831f 100644 --- a/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc +++ b/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc @@ -28,7 +28,7 @@ here, however, you’ll want to think not only from the customer perspective in terms of how the data is written, but also in terms of how the data will be queried by downstream use cases. -You natural tendency as might be to focus first on designing the tables +Your natural tendency might be to focus first on designing the tables to store reservation and guest records, and only then start thinking about the queries that would access them. You may have felt a similar tension already when discussing the shopping queries before, thinking diff --git a/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc b/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc index b478df14a1..2acd6cc2bf 100644 --- a/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc +++ b/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc @@ -17,7 +17,7 @@ image::data_modeling_hotel_relational.png[image] == Design Differences Between RDBMS and Cassandra Let’s take a minute to highlight some of the key differences in doing -ata modeling for Cassandra versus a relational database. +data modeling for Cassandra versus a relational database. === No joins diff --git a/doc/modules/cassandra/pages/getting_started/production.adoc b/doc/modules/cassandra/pages/getting_started/production.adoc index de7fb54234..93b26084b2 100644 --- a/doc/modules/cassandra/pages/getting_started/production.adoc +++ b/doc/modules/cassandra/pages/getting_started/production.adoc @@ -51,7 +51,7 @@ appropriate number of replicates, to ensure even token allocation. Read ahead is an operating system feature that attempts to keep as much data as possible loaded in the page cache. Spinning disks can have long seek times causing high latency, so additional -throughout on reads using page cache can improve performance. +throughput on reads using page cache can improve performance. By leveraging read ahead, the OS can pull additional data into memory without the cost of additional seeks. This method works well when the available RAM is greater than the size of the - 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-3.11' into cassandra-4.0
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 1929550fc07ff938a7ddce36e55df16e46501801 Merge: b183e1f0de 90d0857d34 Author: Mick Semb Wever AuthorDate: Sat Apr 29 18:24:24 2023 +0200 Merge branch 'cassandra-3.11' into cassandra-4.0 doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc | 2 +- doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc | 2 +- doc/modules/cassandra/pages/getting_started/production.adoc | 2 +- 3 files changed, 3 insertions(+), 3 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. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit d7314a5988581dd5a8d505b1d66bd1ff1ba647f0 Merge: 998a98eae8 cfabddcfb0 Author: Mick Semb Wever AuthorDate: Sat Apr 29 19:12:51 2023 +0200 Merge branch 'cassandra-4.1' into trunk - 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.0' into cassandra-4.1
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git commit cfabddcfb0ac6374851aa8ed024992a3cf5000a4 Merge: 1a72fbd9c6 1929550fc0 Author: Mick Semb Wever AuthorDate: Sat Apr 29 19:01:00 2023 +0200 Merge branch 'cassandra-4.0' into cassandra-4.1 doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc | 2 +- doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc | 2 +- doc/modules/cassandra/pages/getting_started/production.adoc | 2 +- 3 files changed, 3 insertions(+), 3 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 (73546f13b -> b1c6e3e05)
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 73546f13b generate docs for 52f24b20 new b1c6e3e05 generate docs for 52f24b20 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 (73546f13b) \ N -- N -- N refs/heads/asf-staging (b1c6e3e05) 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: .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../3.11/cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../4.0/cassandra/getting_started/production.html |2 +- .../data_modeling/data_modeling_queries.html |2 +- .../data_modeling/data_modeling_rdbms.html |2 +- .../4.1/cassandra/getting_started/production.html |2 +- content/doc/4.2/cassandra/architecture/dynamo.html | 145 +- .../doc/4.2/cassandra/architecture/guarantees.html | 145 +- content/doc/4.2/cassandra/architecture/index.html | 147 +- .../doc/4.2/cassandra/architecture/messaging.html | 145 +- .../doc/4.2/cassandra/architecture/overview.html | 147 +- content/doc/4.2/cassandra/architecture/snitch.html | 145 +- .../cassandra/architecture/storage-engine.html}| 154 +- .../doc/4.2/cassandra/architecture/streaming.html | 145 +- .../configuration/cass_cl_archive_file.html| 979 .../configuration/cass_jvm_options_file.html | 924 .../cassandra/configuration/cass_rackdc_file.html | 1030 .../cassandra/configuration/cass_topo_file.html| 954 .../cassandra/configuration/cass_yaml_file.html| 5569 content/doc/4.2/cassandra/configuration/index.html | 919 .../4.2/cassandra/cql/dynamic_data_masking.html| 1241 - content/doc/4.2/cassandra/cql/indexes.html | 983 content/doc/4.2/cassandra/cql/triggers.html| 957 .../data_modeling/data_modeling_conceptual.html| 945 .../data_modeling/data_modeling_physical.html | 1022 .../data_modeling/data_modeling_queries.html | 984 .../data_modeling/data_modeling_schema.html| 1026 .../data_modeling/data_modeling_tools.html | 949 content/doc/4.2/cassandra/data_modeling/index.html | 922 .../cassandra/developing}/cql/SASI.html
[jira] [Updated] (CASSANDRA-18400) Nodetool info should report on the new networking cache
[
https://issues.apache.org/jira/browse/CASSANDRA-18400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-18400:
---
Description:
CASSANDRA-15229 separated the chunk and network cache, creating a new
network_cache_size parameter.
However, *nodetool info* does not report the in-use size of this cache or a hit
ratio as it does for key, row, counter and chunk cache.
{quote}Exceptions : 4
Key Cache : entries 2852, size 297.59 KiB, capacity 100 MiB, 2406561 hits,
2409424 requests, 0.999 recent hit rate, 14400 save period in seconds
Row Cache : entries 0, size 0 bytes, capacity 0 bytes, 0 hits, 0 requests, NaN
recent hit rate, 0 save period in seconds
Counter Cache : entries 0, size 0 bytes, capacity 50 MiB, 0 hits, 0 requests,
NaN recent hit rate, 7200 save period in seconds
Chunk Cache : entries 1118, size 55.02 MiB, capacity 992 MiB, 4695794 misses,
7179421 requests, 0.346 recent hit rate, 24.145 microseconds miss latency
Percent Repaired : 0.0%
{quote}
However, when its full, it will be logged:
{quote}[INFO ] [epollEventLoopGroup-5-12] cluster_id=1 ip_address=127.1.1.1
NoSpamLogger.java:92 - Maximum memory usage reached (128.000MiB), cannot
allocate chunk of 8.000MiB
{quote}
It should report a line similar to the above:
{quote}Network Cache : entries ?, size ? MiB, capacity ? MiB, ? misses, ?
requests, ? recent hit rate
{quote}
Also, not sure why the above show NaN for row and counter cache, is there is a
divide by zero error when the entries are zero?
was:
CASSANDRA-15229 separated the chunk and network cache, creating a new
network_cache_size parameter.
However, *nodetool info* does not report the in-use size of this cache or a hit
ratio as it does for key, row, counter and chunk cache.
{quote}Exceptions : 4
Key Cache : entries 2852, size 297.59 KiB, capacity 100 MiB, 2406561 hits,
2409424 requests, 0.999 recent hit rate, 14400 save period in seconds
Row Cache : entries 0, size 0 bytes, capacity 0 bytes, 0 hits, 0 requests, NaN
recent hit rate, 0 save period in seconds
Counter Cache : entries 0, size 0 bytes, capacity 50 MiB, 0 hits, 0 requests,
NaN recent hit rate, 7200 save period in seconds
Chunk Cache : entries 1118, size 55.02 MiB, capacity 992 MiB, 4695794 misses,
7179421 requests, 0.346 recent hit rate, 24.145 microseconds miss latency
Percent Repaired : 0.0%
{quote}
However, when its full, it will be logged:
{quote}[INFO ] [epollEventLoopGroup-5-12] cluster_id=1 ip_address=127.1.1.1
NoSpamLogger.java:92 - Maximum memory usage reached (128.000MiB), cannot
allocate chunk of 8.000MiB
{quote}
> Nodetool info should report on the new networking cache
> ---
>
> Key: CASSANDRA-18400
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18400
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
>Reporter: Brad Schoening
>Assignee: Ningzi Zhan
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> CASSANDRA-15229 separated the chunk and network cache, creating a new
> network_cache_size parameter.
> However, *nodetool info* does not report the in-use size of this cache or a
> hit ratio as it does for key, row, counter and chunk cache.
> {quote}Exceptions : 4
> Key Cache : entries 2852, size 297.59 KiB, capacity 100 MiB, 2406561 hits,
> 2409424 requests, 0.999 recent hit rate, 14400 save period in seconds
> Row Cache : entries 0, size 0 bytes, capacity 0 bytes, 0 hits, 0 requests,
> NaN recent hit rate, 0 save period in seconds
> Counter Cache : entries 0, size 0 bytes, capacity 50 MiB, 0 hits, 0 requests,
> NaN recent hit rate, 7200 save period in seconds
> Chunk Cache : entries 1118, size 55.02 MiB, capacity 992 MiB, 4695794 misses,
> 7179421 requests, 0.346 recent hit rate, 24.145 microseconds miss latency
> Percent Repaired : 0.0%
> {quote}
> However, when its full, it will be logged:
> {quote}[INFO ] [epollEventLoopGroup-5-12] cluster_id=1 ip_address=127.1.1.1
> NoSpamLogger.java:92 - Maximum memory usage reached (128.000MiB), cannot
> allocate chunk of 8.000MiB
> {quote}
> It should report a line similar to the above:
> {quote}Network Cache : entries ?, size ? MiB, capacity ? MiB, ? misses, ?
> requests, ? recent hit rate
> {quote}
> Also, not sure why the above show NaN for row and counter cache, is there is
> a divide by zero error when the entries are zero?
--
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-16787) Copy from csv file with duration type fields fails to import
[
https://issues.apache.org/jira/browse/CASSANDRA-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-16787:
---
Description:
Getting error:
{code:java}
cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv' WITH
HEADER = FALSE AND NULL='null';
Using 3 child processes
Starting copy of users.user_credentials_by_email with columns [email,
la_duration].
Failed to make batch statement: Received an argument of invalid type for column
"la_duration". Expected: , Got: ; (DurationType arguments must be a Duration.)_
Failed to import 1 rows: TypeError - Received an argument of invalid type for
column "la_duration". Expected: , Got:
; (DurationType arguments must be a Duration.), given up without
retries
Failed to process 1 rows; failed rows written to
import_users_user_credentials_by_email.err
Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
0 rows imported from 1 files in 0.431 seconds (0 skipped).
{code}
*To Reproduce:*
{code:java}
CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
'replication_factor' : 1 } AND durable_writes = true;
CREATE TABLE users.user_credentials_by_email (
email text,
la_duration duration,
PRIMARY KEY(email)
);
{code}
create users.csv file with:
{code:java}
l...@la.com,8m26s482ms
{code}
Run:
{code:java}
COPY users.user_credentials_by_email FROM '/home/automaton/users.csv' WITH
HEADER = FALSE AND NULL='null';
{code}
was:
Getting error:
{code:java}
cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv' WITH
HEADER = FALSE AND NULL='null';
Using 3 child processes
Starting copy of users.user_credentials_by_email with columns [email,
la_duration].
Failed to make batch statement: Received an argument of invalid type for column
"la_duration". Expected: , Got: ; (DurationType arguments must be a Duration.)_
Failed to import 1 rows: TypeError - Received an argument of invalid type for
column "la_duration". Expected: , Got:
; (DurationType arguments must be a Duration.), given up without
retries
Failed to process 1 rows; failed rows written to
import_users_user_credentials_by_email.err
Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
0 rows imported from 1 files in 0.431 seconds (0 skipped).
{code}
*To Reproduce:*
{code:java}
CREATE KEYSPACE users WITH replication = {'class': 'NetworkTopologyStrategy',
'datacenter1': '1'} AND durable_writes = true;
CREATE TABLE users.user_credentials_by_email (
email text,
la_duration duration,
PRIMARY KEY(email)
);
{code}
create users.csv file with:
{code:java}
l...@la.com,8m26s482ms
{code}
Run:
{code:java}
COPY users.user_credentials_by_email FROM '/home/automaton/users.csv' WITH
HEADER = FALSE AND NULL='null';
{code}
> Copy from csv file with duration type fields fails to import
>
>
> Key: CASSANDRA-16787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16787
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Brijesh Dungarakoti
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: error_cassandra_copy_from_1.JPG,
> error_cassandra_copy_from_2.JPG
>
>
> Getting error:
> {code:java}
> cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv'
> WITH HEADER = FALSE AND NULL='null';
> Using 3 child processes
> Starting copy of users.user_credentials_by_email with columns [email,
> la_duration].
> Failed to make batch statement: Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.)_
> Failed to import 1 rows: TypeError - Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.), given up
> without retries
> Failed to process 1 rows; failed rows written to
> import_users_user_credentials_by_email.err
> Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
> 0 rows imported from 1 files in 0.431 seconds (0 skipped).
> {code}
> *To Reproduce:*
> {code:java}
> CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor' : 1 } AND durable_writes = true;
> CREATE TABLE users.user_credentials_by_email (
> email text,
> la_duration duration,
> PRIMARY KEY(email)
> );
> {code}
> create users.csv file with:
> {code:java}
> l...@la.com,8m26s482ms
> {code}
> Run:
> {code:java}
> COPY users.user_credentials_by_email FROM '/home/automaton/users.csv' WITH
> HEADER = FALSE AND NULL='null';
> {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.apa
[jira] [Comment Edited] (CASSANDRA-16787) Copy from csv file with duration type fields fails to import
[
https://issues.apache.org/jira/browse/CASSANDRA-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718006#comment-17718006
]
Brad Schoening edited comment on CASSANDRA-16787 at 4/30/23 2:17 AM:
-
[~brigesh.dungarakoti] [~blerer] [~smiklosovic] As noted in
[CASSANDRA-11873,|http://example.com/] The DataStax Python driver does not
appear to support parsing ISO 8601 formatted strings, which defines several
formats for duration strings. There is a
[cassandra.util|https://github.com/datastax/python-driver/blob/master/cassandra/util.py]
*Duration* class in the driver, but it works with a custom syntax of weeks,
days, and nanoseconds. The library [isodate|https://pypi.org/project/isodate/]
is commonly used to support parsing ISO strings and could be used here to
properly support ISO duration parsing and formating.
It seems to me that deciding upon and placing the library dependency of isodate
(or an alternative) and implementing the behavior in the driver would offer the
most effective solution for parsing the ISO 8601 string formats instead of
bolting it on here. This was mentioned by [~thobbs] in the comments of
CASSANDRA-11873:
{noformat}
Last, it looks like COPY FROM doesn't handle duration values when prepared
statements are used, but I suppose we need duration support in the python
driver for that to be supported.{noformat}
was (Author: bschoeni):
[~brigesh.dungarakoti] [~blerer] [~smiklosovic] As noted in
[CASSANDRA-11873|http://example.com]https://issues.apache.org/jira/browse/CASSANDRA-11873]
The DataStax Python driver does not appear to support parsing ISO 8601
formatted strings, which defines several formats for duration strings. There
is a
[cassandra.util|https://github.com/datastax/python-driver/blob/master/cassandra/util.py]
*Duration* class in the driver, but it works with a custom syntax of weeks,
days, and nanoseconds. The library [isodate|https://pypi.org/project/isodate/]
is commonly used to support parsing ISO strings and could be used here to
properly support ISO duration parsing and formmating.
It seems to me that deciding upon and placing the library dependency of isodate
(or an alternative) and implementing the behavior in the driver would offer the
most effective solution for parsing the ISO 8601 string formats instead of
bolting it on here. This was mentioned by [~thobbs] in the comments of
CASSANDRA-11873:
{noformat}
Last, it looks like COPY FROM doesn't handle duration values when prepared
statements are used, but I suppose we need duration support in the python
driver for that to be supported.{noformat}
> Copy from csv file with duration type fields fails to import
>
>
> Key: CASSANDRA-16787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16787
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Brijesh Dungarakoti
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: error_cassandra_copy_from_1.JPG,
> error_cassandra_copy_from_2.JPG
>
>
> Getting error:
> {code:java}
> cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv'
> WITH HEADER = FALSE AND NULL='null';
> Using 3 child processes
> Starting copy of users.user_credentials_by_email with columns [email,
> la_duration].
> Failed to make batch statement: Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.)_
> Failed to import 1 rows: TypeError - Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.), given up
> without retries
> Failed to process 1 rows; failed rows written to
> import_users_user_credentials_by_email.err
> Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
> 0 rows imported from 1 files in 0.431 seconds (0 skipped).
> {code}
> *To Reproduce:*
> {code:java}
> CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor' : 1 } AND durable_writes = true;
> CREATE TABLE users.user_credentials_by_email (
> email text,
> la_duration duration,
> PRIMARY KEY(email)
> );
> {code}
> create users.csv file with:
> {code:java}
> l...@la.com,8m26s482ms
> {code}
> Run:
> {code:java}
> COPY users.user_credentials_by_email FROM '/home/automaton/users.csv' WITH
> HEADER = FALSE AND NULL='null';
> {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-16787) Copy from csv file with duration type fields fails to import
[
https://issues.apache.org/jira/browse/CASSANDRA-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718006#comment-17718006
]
Brad Schoening commented on CASSANDRA-16787:
[~brigesh.dungarakoti] [~blerer] [~smiklosovic] As noted in
[CASSANDRA-11873|http://example.com]https://issues.apache.org/jira/browse/CASSANDRA-11873]
The DataStax Python driver does not appear to support parsing ISO 8601
formatted strings, which defines several formats for duration strings. There
is a
[cassandra.util|https://github.com/datastax/python-driver/blob/master/cassandra/util.py]
*Duration* class in the driver, but it works with a custom syntax of weeks,
days, and nanoseconds. The library [isodate|https://pypi.org/project/isodate/]
is commonly used to support parsing ISO strings and could be used here to
properly support ISO duration parsing and formmating.
It seems to me that deciding upon and placing the library dependency of isodate
(or an alternative) and implementing the behavior in the driver would offer the
most effective solution for parsing the ISO 8601 string formats instead of
bolting it on here. This was mentioned by [~thobbs] in the comments of
CASSANDRA-11873:
{noformat}
Last, it looks like COPY FROM doesn't handle duration values when prepared
statements are used, but I suppose we need duration support in the python
driver for that to be supported.{noformat}
> Copy from csv file with duration type fields fails to import
>
>
> Key: CASSANDRA-16787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16787
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Brijesh Dungarakoti
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: error_cassandra_copy_from_1.JPG,
> error_cassandra_copy_from_2.JPG
>
>
> Getting error:
> {code:java}
> cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv'
> WITH HEADER = FALSE AND NULL='null';
> Using 3 child processes
> Starting copy of users.user_credentials_by_email with columns [email,
> la_duration].
> Failed to make batch statement: Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.)_
> Failed to import 1 rows: TypeError - Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.), given up
> without retries
> Failed to process 1 rows; failed rows written to
> import_users_user_credentials_by_email.err
> Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
> 0 rows imported from 1 files in 0.431 seconds (0 skipped).
> {code}
> *To Reproduce:*
> {code:java}
> CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor' : 1 } AND durable_writes = true;
> CREATE TABLE users.user_credentials_by_email (
> email text,
> la_duration duration,
> PRIMARY KEY(email)
> );
> {code}
> create users.csv file with:
> {code:java}
> l...@la.com,8m26s482ms
> {code}
> Run:
> {code:java}
> COPY users.user_credentials_by_email FROM '/home/automaton/users.csv' WITH
> HEADER = FALSE AND NULL='null';
> {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] [Comment Edited] (CASSANDRA-16787) Copy from csv file with duration type fields fails to import
[
https://issues.apache.org/jira/browse/CASSANDRA-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718006#comment-17718006
]
Brad Schoening edited comment on CASSANDRA-16787 at 4/30/23 2:19 AM:
-
[~brigesh.dungarakoti] [~blerer] [~smiklosovic] As noted in
[CASSANDRA-11873,|http://example.com/] The DataStax Python driver does not
appear to support parsing ISO 8601 formatted strings, which defines several
formats for duration strings. There is a
[cassandra.util|https://github.com/datastax/python-driver/blob/master/cassandra/util.py]
*Duration* class in the driver, but it works with a custom syntax of weeks,
days, and nanoseconds. The library [isodate|https://pypi.org/project/isodate/]
is commonly used to support parsing ISO strings and could be used here to
properly support ISO duration parsing and formating.
It seems to me that deciding upon and placing the library dependency of isodate
(or an alternative) and implementing the behavior in the driver would offer the
most effective solution for parsing the ISO 8601 string formats instead of
bolting it on here. This was mentioned by [~thobbs] in the comments of
CASSANDRA-11873:
{noformat}
Last, it looks like COPY FROM doesn't handle duration values when prepared
statements are used, but I suppose we need duration support in the python
driver for that to be supported.{noformat}
was (Author: bschoeni):
[~brigesh.dungarakoti] [~blerer] [~smiklosovic] As noted in
[CASSANDRA-11873,|http://example.com/] The DataStax Python driver does not
appear to support parsing ISO 8601 formatted strings, which defines several
formats for duration strings. There is a
[cassandra.util|https://github.com/datastax/python-driver/blob/master/cassandra/util.py]
*Duration* class in the driver, but it works with a custom syntax of weeks,
days, and nanoseconds. The library [isodate|https://pypi.org/project/isodate/]
is commonly used to support parsing ISO strings and could be used here to
properly support ISO duration parsing and formating.
It seems to me that deciding upon and placing the library dependency of isodate
(or an alternative) and implementing the behavior in the driver would offer the
most effective solution for parsing the ISO 8601 string formats instead of
bolting it on here. This was mentioned by [~thobbs] in the comments of
CASSANDRA-11873:
{noformat}
Last, it looks like COPY FROM doesn't handle duration values when prepared
statements are used, but I suppose we need duration support in the python
driver for that to be supported.{noformat}
> Copy from csv file with duration type fields fails to import
>
>
> Key: CASSANDRA-16787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16787
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Brijesh Dungarakoti
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: error_cassandra_copy_from_1.JPG,
> error_cassandra_copy_from_2.JPG
>
>
> Getting error:
> {code:java}
> cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv'
> WITH HEADER = FALSE AND NULL='null';
> Using 3 child processes
> Starting copy of users.user_credentials_by_email with columns [email,
> la_duration].
> Failed to make batch statement: Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.)_
> Failed to import 1 rows: TypeError - Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.), given up
> without retries
> Failed to process 1 rows; failed rows written to
> import_users_user_credentials_by_email.err
> Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
> 0 rows imported from 1 files in 0.431 seconds (0 skipped).
> {code}
> *To Reproduce:*
> {code:java}
> CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor' : 1 } AND durable_writes = true;
> CREATE TABLE users.user_credentials_by_email (
> email text,
> la_duration duration,
> PRIMARY KEY(email)
> );
> {code}
> create users.csv file with:
> {code:java}
> l...@la.com,8m26s482ms
> {code}
> Run:
> {code:java}
> COPY users.user_credentials_by_email FROM '/home/automaton/users.csv' WITH
> HEADER = FALSE AND NULL='null';
> {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] [Updated] (CASSANDRA-16787) Copy from csv file with duration type fields fails to import
[
https://issues.apache.org/jira/browse/CASSANDRA-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-16787:
---
Description:
Getting error:
{code:java}
cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv' WITH
HEADER = FALSE AND NULL='null';
Using 3 child processes
Starting copy of users.user_credentials_by_email with columns [email,
la_duration].
Failed to make batch statement: Received an argument of invalid type for column
"la_duration". Expected: , Got: ; (DurationType arguments must be a Duration.)_
Failed to import 1 rows: TypeError - Received an argument of invalid type for
column "la_duration". Expected: , Got:
; (DurationType arguments must be a Duration.), given up without
retries
Failed to process 1 rows; failed rows written to
import_users_user_credentials_by_email.err
Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
0 rows imported from 1 files in 0.431 seconds (0 skipped).
{code}
*To Reproduce:*
{code:java}
CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
'replication_factor' : 1 } AND durable_writes = true;
CREATE TABLE users.user_credentials_by_email (
email text,
la_duration duration,
PRIMARY KEY(email)
);
{code}
create users.csv file with:
{code:java}
l...@la.com,8m26s482ms
{code}
Run:
{code:java}
COPY users.user_credentials_by_email FROM 'users.csv' WITH HEADER = FALSE AND
NULL='null';
{code}
was:
Getting error:
{code:java}
cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv' WITH
HEADER = FALSE AND NULL='null';
Using 3 child processes
Starting copy of users.user_credentials_by_email with columns [email,
la_duration].
Failed to make batch statement: Received an argument of invalid type for column
"la_duration". Expected: , Got: ; (DurationType arguments must be a Duration.)_
Failed to import 1 rows: TypeError - Received an argument of invalid type for
column "la_duration". Expected: , Got:
; (DurationType arguments must be a Duration.), given up without
retries
Failed to process 1 rows; failed rows written to
import_users_user_credentials_by_email.err
Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
0 rows imported from 1 files in 0.431 seconds (0 skipped).
{code}
*To Reproduce:*
{code:java}
CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
'replication_factor' : 1 } AND durable_writes = true;
CREATE TABLE users.user_credentials_by_email (
email text,
la_duration duration,
PRIMARY KEY(email)
);
{code}
create users.csv file with:
{code:java}
l...@la.com,8m26s482ms
{code}
Run:
{code:java}
COPY users.user_credentials_by_email FROM '/home/automaton/users.csv' WITH
HEADER = FALSE AND NULL='null';
{code}
> Copy from csv file with duration type fields fails to import
>
>
> Key: CASSANDRA-16787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16787
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Brijesh Dungarakoti
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: error_cassandra_copy_from_1.JPG,
> error_cassandra_copy_from_2.JPG
>
>
> Getting error:
> {code:java}
> cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv'
> WITH HEADER = FALSE AND NULL='null';
> Using 3 child processes
> Starting copy of users.user_credentials_by_email with columns [email,
> la_duration].
> Failed to make batch statement: Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.)_
> Failed to import 1 rows: TypeError - Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.), given up
> without retries
> Failed to process 1 rows; failed rows written to
> import_users_user_credentials_by_email.err
> Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
> 0 rows imported from 1 files in 0.431 seconds (0 skipped).
> {code}
> *To Reproduce:*
> {code:java}
> CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor' : 1 } AND durable_writes = true;
> CREATE TABLE users.user_credentials_by_email (
> email text,
> la_duration duration,
> PRIMARY KEY(email)
> );
> {code}
> create users.csv file with:
> {code:java}
> l...@la.com,8m26s482ms
> {code}
> Run:
> {code:java}
> COPY users.user_credentials_by_email FROM 'users.csv' WITH HEADER = FALSE AND
> NULL='null';
> {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] [Assigned] (CASSANDRA-16787) Copy from csv file with duration type fields fails to import
[
https://issues.apache.org/jira/browse/CASSANDRA-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening reassigned CASSANDRA-16787:
--
Assignee: (was: Brad Schoening)
> Copy from csv file with duration type fields fails to import
>
>
> Key: CASSANDRA-16787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16787
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Brijesh Dungarakoti
>Priority: Normal
> Fix For: 4.0.x
>
> Attachments: error_cassandra_copy_from_1.JPG,
> error_cassandra_copy_from_2.JPG
>
>
> Getting error:
> {code:java}
> cqlsh> COPY users.user_credentials_by_email FROM '/home/ubuntu/users.csv'
> WITH HEADER = FALSE AND NULL='null';
> Using 3 child processes
> Starting copy of users.user_credentials_by_email with columns [email,
> la_duration].
> Failed to make batch statement: Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.)_
> Failed to import 1 rows: TypeError - Received an argument of invalid type for
> column "la_duration". Expected: ,
> Got: ; (DurationType arguments must be a Duration.), given up
> without retries
> Failed to process 1 rows; failed rows written to
> import_users_user_credentials_by_email.err
> Processed: 1 rows; Rate: 2 rows/s; Avg. rate: 2 rows/s
> 0 rows imported from 1 files in 0.431 seconds (0 skipped).
> {code}
> *To Reproduce:*
> {code:java}
> CREATE KEYSPACE users WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor' : 1 } AND durable_writes = true;
> CREATE TABLE users.user_credentials_by_email (
> email text,
> la_duration duration,
> PRIMARY KEY(email)
> );
> {code}
> create users.csv file with:
> {code:java}
> l...@la.com,8m26s482ms
> {code}
> Run:
> {code:java}
> COPY users.user_credentials_by_email FROM 'users.csv' WITH HEADER = FALSE AND
> NULL='null';
> {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
[cassandra-website] branch asf-staging updated (b1c6e3e05 -> 530e053f4)
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 b1c6e3e05 generate docs for 52f24b20 new 530e053f4 generate docs for 52f24b20 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 (b1c6e3e05) \ N -- N -- N refs/heads/asf-staging (530e053f4) 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 (530e053f4 -> 9f0dea1b9)
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 530e053f4 generate docs for 52f24b20 new 9f0dea1b9 generate docs for 52f24b20 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 (530e053f4) \ N -- N -- N refs/heads/asf-staging (9f0dea1b9) 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 (9f0dea1b9 -> d68bf23cc)
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 9f0dea1b9 generate docs for 52f24b20 new d68bf23cc generate docs for 52f24b20 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 (9f0dea1b9) \ N -- N -- N refs/heads/asf-staging (d68bf23cc) 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
