Hi,
We are running version 7.5.1.
Did anything I submitted describe what we are doing in detail.
1-I have shown the mapping
2-I shown our indexing Code
3-And the result
What else can I provide for you to see the problem?
It may also be an idea for you to at least use the same kind of object with several properties as opposed to a single one in order for you to properly evaluate this scenario otherwise we will not be getting like for like!!!
What is the point of showing code that works which LOOKS NOTHING LIKE the problem that is being looked at!!!
when you are in a position to exchange more than 1 message per week, please let us know so that we can communicate.
In the meantime, if you really want to help Elasticsearch, just bin this library so that people won't get diluted and suffer using it thinking that it is a productivity tool where it is actually a Detrimental tool.
We have never come across a library that HINDERS development as much as NEST does!
@han1 the suggestion from the information you've provided is that indexing a document with a nested mapping is crashing the application. This cannot be replicated locally or running against Elastic Cloud as @Martijn_Laarman showed, and does not show up in the integration tests either. What Martijn is highlighting is that the information provided is insufficient to understand where the problem is, hence we are asking for more information and a small example that reproduces the problem.
Please also note we've pointed out our code of conduct a few times now, you agreed to abide by this when you created an account. If you are unable to remain civil and courteous and respond constructively to those that are trying to assist you then we will close this thread.
We will try and get the hell out of everything Elastic as soon as possible but that will take us some time. If you are INCAPABLE of sorting even a simple issue like this, then don't get hot under the color when someone calls your incompetence out!
If we produced products like this, our clients would laugh at us. You seem to think we should be grateful!
As they say. The best way to know an organisation is to do business with them. We have certainly got to know you!
I have already provided everything possible. What else do you need to know to work out where your product is falling down!
So somewhere in between my setup and yours something seems to not go right, any thing that sticks out to you or more that you can share about your setup?
Now how helpful is that - somewhere in between is basically the wire (internet). What would you like me to provide. The bits on the wire?
What he has provided about his set up- is what I have also provided.
The indexing works - EVERYTHING works! New documents can be indexed and updated without problem AS LONG AS the nested object is not set.
BUT, when you set the nested object - Then CRASH.
Can he AT LEAST create the same Nested object with the same number of properties and types as I have indicated in my code so that we can see like for like as opposed to something that has nothing to do with the problem at hand?
That's exactly the reason I asked you earlier if you could share with us a minimal project that helps to reproduce the problem.
I'm not a .Net dev so I can't help myself on that. I'm a Java dev and if it was Java code, I'd likely suspect something in the way the Java beans are been executed by the JVM.
So thank you so far for the details you provided. It would be even better and faster if you could share on GitHub or somewhere else the .Net objects you are using (not sure I'm using the right terminology though).
@han1 I created the small reproduction for several reasons:
Your examples are incomplete the mapping you provide does not correlate with the index call that you stated.
As mentioned we have >3000 integration test most of which rely on a rich document being indexed with a nested mapping. These tests run on commit against 6 different elasticsearch versions, multiple elasticsearch instances within a version as well as testing Windows and Linux. I am not convinced it has anything to do with the number of properties. But do not rule anything out at the moment.
The goal of starting small was to find the difference between what I know works and your setup.
I shall try to respond to these - But tell me - Is there any reason you are not using the same type of object that we are using and using something COMPLETELY unrelated to this problem?
1-What does your ElasticsearchConfig.GetClient() look like, where does it deviate from the simple reproduction setup?
return new ElasticClient(_connectionSettings);
_connectionSettings = new ConnectionSettings(CreateUri(/*9200*/))
.BasicAuthentication("elastic", Startup.ConfigurationStatic["Elastic:ClusterAddress"])
.DisableDirectStreaming(true);
What operating systems do you use? Windows 10
What version of .NET are you using? Core 3.1
What version of the client are you using? 7.5.1
Where does your .NET code run? Console App? MVC? IIS? Kestrel? Azure Functions? MVC Core 3.1
Can you share more information about the actual des C# class that you are trying to index an instance of? The class is shown in the NEST mapping - A simple POCO with 7 properties as shown!
Is any part of your C# class using or the invocatation using dynamic or ExpandoObject? -No.
Does my small reproduction work on your end? Even if it does it is useless as your repproduction is not a reporduction as we KEEP trying to tell you.
If your on windows do you see a correlating event in the Event Viewer for the crash? - NO
The answer to the serialization is that it also does not help.
Can you elaborate:
** Your examples are incomplete the mapping you provide does not correlate with the index call that you stated.**
What does not correlate - Have you looked at the stuff we provided?
The questions you are asking seems to be debugging our ability to connect to Elasticsearch and perform operations.
As we have already mentioned - EVERYTHING WORKS EXCEPT when a nested property is involved.
Our ES connection string, OS, .NET Version, Client Version are all 100% as the system works - EXCEPT when there is a nested property involved.
The only indexing call with a nested field you've provided on this thread:
var doc = new des{prop1=1, prop2=2, nestedFiled=so sn so}
var result = await ElasticSearchConfig.GetClient().IndexAsync(doc, idx => idx.Index($"properties-{dest.Country.ToLower()}"));
Which is not valid C# nor have you provided the C# POCO corresponding to des or your mapping. Which forced me to use my own.
Even if it does it is useless as your repproduction is not a reporduction as we KEEP trying to tell you.
Its indexing a POCO that has a nested mapping, happy to use your POCO instead to more closely match your setup.
Can you still let me know the answer to the following questions:
Do you also get the crash if you do call
var serialized = client.SourceSerializer.SerializeToString(objectYouWantToIndex);
var serialized = client.RequestResponseSerializer.SerializeToString(objectYouWantToIndex)
The questions you are asking seems to be debugging our ability to connect to Elasticsearch and perform operations.
I can assure you this is not the case, my only goal here is to get the the bottom of this.
I've touched on what I was missing 2 replies ago and even went as far as to try to fill in the gaps in the following reply.
I have no interest exploring this further if your hell bend on just seeming to be looking for canning fodder in my replies. This is turning incredibly unproductive.
You mean the statement you made had absolutely no basis. Thought so.
Look. Your questions are so irrelevant that it is obvious why we are not getting anywhere.
Is there anyone more senior you can put on this so that we can sort this out before the next Millennium!
That's sad that you didn't want to help by answering the question we asked.
I believe we can not help more here until you answer and help us to help you.
Are you KIDDING? Do you see the thread? or are you just making things up!
The fact of the matter is that there is NO SENSE OF RESPONSIBILITY, DIGNITY OR INTEGRITY in this company and the quicker we are rid of it the better.
Thank goodness for those who are locked into it that the main part (Lucene) is written by someone else otherwise god knows what RUBBISH would be coming out if NEST is an example of your competence.
TALK IS CHEAP. ACTION IS WHAT COUNTS!
And there is nothing from you.
You guys think there is no Justice in this world so anything goes - take their money when it suits and let them hang when it does not. And you are actually right 99.9999999999..... of the time. But when Justice raises its glorious head just once in a lifetime then....
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.