Oleksandr Kolomiiets
Oleksandr Kolomiiets
Hi everyone, are there any updates on this? Current sfproj format causes annoying issues like https://github.com/Azure/service-fabric-issues/issues/840 when using ASP.NET Core projects with Fabric. Basically recommended for such projects "dotnet restore"...
I would like to see this change. I was surprised to see `body` on `Response` returning `Result` because i didn't see a way to handle it properly. As a result...
Recommended usage of `murmur3` field is as a multi field to achieve a speedup in cardinality queries. As a multi field it won't impact synthetic source generation, source will be...
@elasticmachine update branch
Synthetic source for ranges is not released yet so it shouldn't be breaking #107081.
@elasticmachine update branch
Here is another interesting observation. Currently `geo_shape` mapper (all of them) defines a block loader that only works with `_source`. It does not look like that infrastructure supports synthetic source...
I am thinking we should opt-in into this one field at a time by setting `supportsSyntheticSourceNatively` (maybe should rename this too).
@elasticmachine update branch
@elasticmachine update branch