Points in the joined series should have either the columns of the left
side or the columns of the right side of the join. Before this patch
join relied on merge to order the points of the two series and then join
consecutive points together. The merge emitted the union of the columns
of the two series, which caused the joined series to always have the
union of two series. This combined with the fact that the point's values
weren't adjusted to have nulls for the missing columns caused panic when
any operation is done on the points, e.g. addition.
Fix#740, Fix#781
This commit fixes two bugs:
Don't try to parse "inf" retention policy when creating a shard
space. This caused a panic to be thrown when a shard space is created
with infinity. Fix#774
`getExpiredShards()` used shard duration to determine which shards are
expired but should be using shard retention duration instead. Close#769
Currently all writes (unless synchronous) have to go through the write
buffer and the WAL in order to guarantee proper replication. This commit
changes the behavior for shards that aren't replicated.
Fix#734.
Previously the graphite plugin required payloads to be space delimited
and didn't like tabs. This commit breaks the payload using any
whitespace delimiter. Fix#707.
Adjust parser to understand queries like 'SELECT * FROM series1, series2, ...'.
It seems that selecting from multiple series was supported everywhere else, but
parser just could not understand the syntax.
Listing cluster admins still returns a list where a 'username' field is used instead of 'user' field. This fix should not affect anything else than that presentation.
John Shahid
Paul Dix
Philip O'Toole
Tony Pitale
Bruno Binet
Jari Sukanen
Mladen Srdic