Commit Graph

8 Commits (2.7)

Author SHA1 Message Date
WeblWabl 5900fcfb17
fix: ensure fields in memory match on disk (#26402)
Co-authored-by: davidby-influx <72418212+davidby-influx@users.noreply.github.com>
closes https://github.com/influxdata/influxdb/issues/26035
2025-05-12 15:11:38 -05:00
WeblWabl eb1dd04706
fix: prevent differing field types in the same shard (#26025) (#26403)
Co-authored-by: davidby-influx <72418212+davidby-influx@users.noreply.github.com>
fix: lock MeasurementFields while validating (#25998)
closes https://github.com/influxdata/influxdb/issues/23756
fix: switch MeasurementFields from atomic.Value to sync.Map (#26022)
closes https://github.com/influxdata/influxdb/issues/26001
2025-05-12 12:52:23 -05:00
Jeffrey Smith II f74c69c5e4
chore: update to go 1.20 (#24088)
* build: upgrade to go 1.19

* chore: bump go.mod

* chore: `gofmt` changes for doc comments

https://tip.golang.org/doc/comment

* test: update tests for new sort order

* chore: make generate-sources

* chore: make generate-sources

* chore: go 1.20

* chore: handle rand.Seed deprecation

* chore: handle rand.Seed deprecation in tests

---------

Co-authored-by: DStrand1 <dstrandboge@influxdata.com>
2023-02-09 14:14:35 -05:00
Daniel Moran 4dd2d7cc7f
fix: hard limit on field size while parsing line protocol (#22311)
Per https://docs.influxdata.com/influxdb/v2.0/reference/syntax/line-protocol/#string
we only support 64KB, but 1MB is a more realistic practical limit. Before this commit there was
no enforcement of field value size.


Co-authored-by: Sam Arnold <sarnold@influxdata.com>
2021-08-27 10:01:17 -04:00
Stuart Carnie dee8977d2c
chore: move v2/v1/tsdb → v2/tsdb 2020-08-26 10:46:47 -07:00
Mark Rushakoff f2898d1992 Wipe out workspace in preparation for v2 merge
"Knock knock."

"Who's there?"

"InfluxDB Veet."

...
2019-01-11 10:38:50 -08:00
Jeff Wendling e5dbc18d0b remove bool return param from dataTypeFromModelsFieldType 2018-04-25 09:48:24 -06:00
Jeff Wendling 29a62e4f74 Add FieldValidator to allow custom validations on measurements
No appreciable changes in benchmark results. It seems like this
function is less than 4% of cpu time in the write workloads in the
benchmarks at least.
2018-04-23 20:21:27 -06:00