# Help: NEST Search Match List\\ARRAY Debacle

**URL:** <https://discuss.elastic.co/t/help-nest-search-match-list-array-debacle/123804>\
**Category:** Elasticsearch\
**Created:** [March 13, 2018, 8:38pm UTC](https://discuss.elastic.co/t/help-nest-search-match-list-array-debacle/123804 "2018-03-13T20:38:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JRod](https://avatars.discourse-cdn.com/v4/letter/j/e480ec/32.png) [@JRod](https://discuss.elastic.co/u/JRod)\
**Post date:** [March 13, 2018, 8:38pm UTC](https://discuss.elastic.co/t/help-nest-search-match-list-array-debacle/123804/1 "2018-03-13T20:38:07Z")

</div>

Hi I was hoping I could get some help on this issue I have been having. The below code works but I want to tweek it to were .MATCH is the one that is actually searching for field2Text1 or field2Text2 in field2. Most sites have always said to use TERMS. But in TERM vs MATCH. I need MATCH's rules to where it is not case sensitive and exact. I like TERMS ability to just have a list dropped into it to search, I was wondering is MATCH had something similiar in NEST.

```
` var response = await esClient.SearchAsync<Results>(s => s
            .AllTypes()
            .From(0)
            .Size(5)
            .Query(q => q
                .Match(m => m
                    .Field(f => f.field1)
                    .Query("field1Text")
                ) && q
                 .Terms(m => m
                     .Field(f => f.field2)
                     .Terms(new List<string> { "field2Text1", "field2Text2" })
                ) && +q
            )

        );`
```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 10, 2018, 8:38pm UTC](https://discuss.elastic.co/t/help-nest-search-match-list-array-debacle/123804/2 "2018-04-10T20:38:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.