2
93%
master: 97%

Ran 01 Feb 2021 12:57PM UTC

Files 37

Run time 4s

Badge

Embed ▾

Committed 01 Feb 2021 12:23PM UTC coverage: 95.543% (-0.5%) from 96.074%

Job # RELEASE=true

Build Type

push

travis-ci-com

Committed by

web-flow

Commit Message

#117: Added exasol-testcontainers for integration tests (#119)

## Added data importer integration tests

## Fixed timestamp integration tests

The Parquet and Avro format store long value (the number of milliseconds
since epoch) as timestamp value. Thus no timezone information is encoded
when writing.

However, when we import the files using Exasol UDFs, we construct a Java
`java.sql.Timestamp` object from the milliseconds since epoch, and emit
them into table. At this moment, the Java Timestamp uses the JVM
timezone. It is usually `Europe/Berlin` for instance for the Exasol
docker container. You can the Exasol system timezone using `DBTIMEZONE`
(`SELECT DBTIMEZONE`).

This introduces a difference integration tests, timestamps written in
UTC is returned in Europe/Berlin timezone. Therefore, we shift the
expected values to database timezone.

This issue does not occur in the Orc format because it also encodes the
timezone information in the file so that Orc readers uses that timezone
(https://github.com/apache/orc/pull/249).

## Added nested suites with single docker container stack

Run Details

836 of 875 relevant lines covered (95.54%)

0.96 hits per line

exasol / cloud-storage-extension / 391 / 2
93%
master: 97%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 391.2 (RELEASE=true)

exasol / cloud-storage-extension / 391 / 2 93% master: 97%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 391.2 (RELEASE=true)

exasol / cloud-storage-extension / 391 / 2
93%
master: 97%

README BADGES
x