Closed
Description
NEST/Elasticsearch.Net version:
7.6.1/7.7
Elasticsearch version:
7.6.2
Runtime/OS info
dotnet 3.1.201 on Mac OS X 10.14.4 (BuildVersion: 18E226)
Description of the problem including expected versus actual behavior:
Indexing a document that contains a property that is a nullable value tuple such as (string info, int number)?
with a value that is not null produces a SIGSEGV
and the whole application crashes.
Steps to reproduce:
The issue can be reproduced with the following code:
using System;
using Nest;
public class ExampleDoc {
public (string info, int number)? tupleNullable { get; set; }
}
public class Program {
public static void Main() {
var node = new Uri("http://localhost:9200");
var client = new ElasticClient(new ConnectionSettings(node));
var doc = new ExampleDoc {
tupleNullable = ("somestring", 42),
};
var indexName= "index4";
client.Indices.Create(indexName, index => index
.Map<ExampleDoc>(m => m
.AutoMap()
));
client.Index(doc, i => i.Index(indexName));
}
}
Expected behavior
The expected bahavior is to either throw an exception if this usecase is not supported or to successfully index the document
Metadata
Metadata
Assignees
Labels
No labels