Unable to filter for Nested property with Ingest pipeline processor query

Elastic Stack Elasticsearch
1

Getting bad request - "The remote server returned an error: (400) Bad Request.. Call: Status code 400 from: POST /infilesearch-v1/es_file/_search?typed_keys=true. ServerError: Type: search_phase_execution_exception Reason: "all shards failed"".

Works well when not using ingest pipeline processor plugin.

Code -
var ss = new List { "content_length", "content_type", "content" };

var tttt= client.PutPipeline("att", p => p
.Description("Document attachment pipeline")
.Processors(pr => pr
.Attachment<ES_File>(a => a
.Field(f => f.Content).IndexedCharacters(-1)
.TargetField(f => f.Attachment)

                          .Properties(ss)
                        )
                        .Remove<ES_File>(r => r
                          .Field(f => f.Content) 
                        )
                      )
                    );

Error Query-
var res = client.Search<ES_File>(s => s.Index("fileIndexName")
.Query
(
q => q.Match(p => p.Field(z => z.Attachment.Content).Query("firm"))
&& q.Nested(e => e.Path(v => v.User).Query(h => h.Match(b => b.Field("User.userid").Query("1"))))));

2

Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.

Or use markdown style like:

```
CODE
```

This is the icon to use if you are not using markdown format:

image
image.jpg764×92 16.4 KB

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
Please update your post.

You probably have also more logs to share or more details in the response.

Could you provide a full recreation script as described in About the Elasticsearch category. It will help to better understand what you are doing. Please, try to keep the example as simple as possible.

A full reproduction script will help readers to understand, reproduce and if needed fix your problem. It will also most likely help to get a faster answer.