This is an automated email from the ASF dual-hosted git repository.
brandonwilliams 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 139ad44 Update docs regarding timestamp precision
139ad44 is described below
commit 139ad44e8b53ed194ba4b47fbfae3484015034f9
Author: Adam Holmberg <[email protected]>
AuthorDate: Thu Aug 13 14:05:18 2020 -0500
Update docs regarding timestamp precision
Patch by Adam Holmberg, reviewed by brandonwilliams for CASSANDRA-14853
---
doc/source/cql/types.rst | 3 +++
doc/source/development/testing.rst | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/doc/source/cql/types.rst b/doc/source/cql/types.rst
index 509a756..783f3d1 100644
--- a/doc/source/cql/types.rst
+++ b/doc/source/cql/types.rst
@@ -153,6 +153,9 @@ The time of day may also be omitted (``'2011-02-03'`` or
``'2011-02-03+0000'``),
default to 00:00:00 in the specified or default time zone. However, if only
the date part is relevant, consider using
the :ref:`date <dates>` type.
+Note: while Cassandra will parse and accept time literals with a greater
number of digits, the value stored will be truncated to
+millisecond precision.
+
.. _dates:
Working with dates
diff --git a/doc/source/development/testing.rst
b/doc/source/development/testing.rst
index 7f38fe5..1f32e12 100644
--- a/doc/source/development/testing.rst
+++ b/doc/source/development/testing.rst
@@ -70,7 +70,7 @@ DTests
One way of doing integration or system testing at larger scale is by using
`dtest <https://github.com/apache/cassandra-dtest>`_, which stands for
“Cassandra Distributed Tests”. The idea is to automatically setup Cassandra
clusters using various configurations and simulate certain use cases you want
to test. This is done using Python scripts and ``ccmlib`` from the `ccm
<https://github.com/pcmanus/ccm>`_ project. Dtests will setup clusters using
this library just as you do running ad-hoc [...]
-Using dtests helps us to prevent regression bugs by continually executing
tests on the `CI server <https://builds.apache.org/>`_ against new patches.
Committers will be able to set up build branches there and your reviewer may
use the CI environment to run tests for your patch. Read more on the motivation
behind continuous integration `here
<http://www.datastax.com/dev/blog/cassandra-testing-improvements-for-developer-convenience-and-confidence>`_.
+Using dtests helps us to prevent regression bugs by continually executing
tests on the `CI server <https://builds.apache.org/>`_ against new patches.
Committers will be able to set up build branches there and your reviewer may
use the CI environment to run tests for your patch.
The best way to learn how to write dtests is probably by reading the
introduction "`How to Write a Dtest
<http://www.datastax.com/dev/blog/how-to-write-a-dtest>`_" and by looking at
existing, recently updated tests in the project. New tests must follow certain
`style conventions
<https://github.com/apache/cassandra-dtest/blob/master/CONTRIBUTING.md>`_ that
are being checked before accepting contributions. In contrast to Cassandra,
dtest issues and pull-requests are managed on github, the [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
