ngageoint / geowave / 1717 / 3
63%
master: 52%

LAST BUILD BRANCH: GEOWAVE-1112
DEFAULT BRANCH: master
Ran
Files 589
Run time 36s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 62.612% (-0.02%) from 62.63%
ACCUMULO_VERSION='1.6.2' ACCUMULO_LEGACY='' HADOOP_VERSION='2.6.0' GEOTOOLS_VERSION='13.1' GEOSERVER_VERSION='2.7.1.1' PLATFORM_VERSION='""'

push

travis-ci

meislerj 
Implemented a Simple NumericIndexStrategy

Created a simple 1-dimensional NumericIndexStrategy that
can index integer values. The strategy doesn't use any
binning. The ids are simply the byte[] values of the numbers.
This index strategy won't work well for inserting ranges
since the data will be replicated for each integer value
in the range.

The SimpleNumericIndexStrategy is an abstract class that
uses a Short, Integer, or Long lexicoder to encode/decode
numbers. This allows for adjusting the size of the keys
(i.e. a 16 or 32 bit integer might give a large enough
range for some applications) to save space in the row ID.
Extended by SimpleShortIndexStrategy (for 16 bit keys),
SimpleIntegerIndexStrategy (for 32 bit keys), and
SimpleLongIndexStrategy (for 64 bit keys).

getQueryRanges always returns 1 range since the sort order of the
bytes is the same as the sort order of the values. This means that
a contiguous range of values can be represented by a single
contiguous ByteArrayRange.

getInsertionIds returns a single insertionId if you are inserting
a point. If you insert a range, you'll get back a list with the
size of the number of integers in the range (because there is no
binning). That is not the intended use of this index strategy.

16040 of 25618 relevant lines covered (62.61%)

0.63 hits per line

Source Files on job 1717.3 (ACCUMULO_VERSION='1.6.2' ACCUMULO_LEGACY='' HADOOP_VERSION='2.6.0' GEOTOOLS_VERSION='13.1' GEOSERVER_VERSION='2.7.1.1' PLATFORM_VERSION='""')