Athena Brown
Athena Brown
`match` query on scaled_float property no longer matches for some values involving loss of precision
I reproduced this on Cloud with the steps in the ticket (reformatted here as Dev Tools syntax for convenience): ``` PUT test-index-2 {"mappings":{"properties":{"myscaled":{"type":"scaled_float","scaling_factor":100.0}}}} POST test-index-2/_doc {"myscaled":"92233720368547750"} GET test-index-2/_search {"query":{"match":{"myscaled":{"query":"92233720368547750"}}}} ```...
@elasticmachine update branch
Failure was https://github.com/elastic/elasticsearch/issues/107503
https://github.com/elastic/elasticsearch/issues/108045
@elasticmachine run elasticsearch-ci/part-3-fips
@elasticmachine update branch
Running it locally, this shows up in the node logs, which makes me suspect this is related to the cause: ``` » [2024-04-26T16:40:28,651][ERROR][o.e.x.s.a.AuthenticatorChain] [v8.1.3-1] caught exception while trying to read...
@jakelandis I believe I've addressed the concerns we discussed, could you give me a review?
@jakelandis I yes-and'd your idea into "create a writeable that streams the equivalent to a get request"; I think that makes it a bit more maintainable while still letting us...
Digging into this, I think the behavior @DaveCTurner describes above should be a separate issue, and is possibly expected behavior. If a node is actually offline, then the migration is...