We have run into an issue here, where having multiple types for the same field can cause issues. For example, consider an index on x.y. If one measurement has {x: 5}, one has {x: <date>}, and one has {x: {y: true}}, then the min will be 5, the max will be <date>, and the bucket will not be indexed since x.y is undefined in min and max.