| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
metaField into an update on its buckets collection
|
| |
|
| |
|
|
|
|
| |
timeseries_list_collections.js
|
|
|
|
| |
timeseries_list_collections_filter_name.js
|
|
|
|
|
|
|
|
|
|
|
|
| |
fixed linter
ts bucket fix
fixed test
Deleted empty line changed collection name
fixed test naming
|
|
|
|
| |
SERVER-56366
|
| |
|
| |
|
|
|
|
| |
replica_sets_initsync_jscore_passthrough.yml
|
|
|
|
| |
collection being time-series, not clustered
|
|
|
|
| |
timeseries collection's metaField
|
|
|
|
| |
metaField only dot notation queries
|
|
|
|
| |
for timeseries collections
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
timeseries bucket collection.
|
| |
|
| |
|
|
|
|
| |
support for text indexes on time-series collections
|
| |
|
| |
|
|
|
|
| |
This reverts commit 7e0bc86f525d56dedca7d8bf9c858d5a8b49fae1.
|
| |
|
|
|
|
| |
minimum bucket time
|
| |
|
|
|
|
| |
from listCollections
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The 'granularity' option specifcies the expected ingestion rate of new
measurements. Valid options are 'seconds', 'minutes', or 'hours'. The
default is 'seconds'.
|
| |
|
|
|
|
|
|
|
| |
optimize traversal perf at the expense of inserts
When users are inserting measurements with a consistent field order we don't need to search and can just traverse the MinMax structure in lock-step with the measurement.
If users do not provide a consistent field order we fallback to map lookup when we reach a certain search threshold to limit impact of linear search.
|
|
|
|
| |
test for more predictable comparison
|
|
|
|
| |
time-series collections
|
| |
|
| |
|
| |
|
|
|
|
| |
with time-series: it is not supported.
|
|
|
|
| |
jstests/core/timeseries/timeseries_special_indexes.js
|
|
|
|
| |
for time series collections.
|
| |
|
|
|
|
| |
replica_sets_initsync_jscore_passthrough.yml
|
| |
|
| |
|